Triple
T30429463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotha |
E774119
|
entity |
| Predicate | TokhuEmongTime |
P169767
|
FINISHED |
| Object | November |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: November | Statement: [Lotha, TokhuEmongTime, November]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TokhuEmongTime Context triple: [Lotha, TokhuEmongTime, November]
-
A.
timeZoneOnChineseSide
Indicates that the referenced time zone is the one used on the Chinese side of a border, boundary, or cross-border context.
-
B.
timeZonePractice
Indicates that an entity conducts activities or operations according to a particular time zone or set of time zone rules.
-
C.
timeZoneOnKoreanSide
Indicates that the referenced time zone is the one used on the Korean side of a border, division, or demarcation line.
-
D.
isThreeQuartersOfAnHourAheadOf
Indicates that one entity’s time occurs exactly 45 minutes later than the other entity’s time.
-
E.
timeSystem
Indicates a relationship where an entity uses, follows, or is defined within a particular system for measuring or organizing time.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6866c549c8190985ef4bf8032209e |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 29, 2026, 8:06 p.m.