Triple
T38396538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trot |
E900776
|
entity |
| Predicate | residenceLater |
P77808
|
FINISHED |
| Object | Emerald City |
—
|
NE NERFINISHED |
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: Emerald City | Statement: [Trot, residenceLater, Emerald City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residenceLater Context triple: [Trot, residenceLater, Emerald City]
-
A.
residenceAfterService
Indicates that an entity’s place of residence is located or established after completing a specified period of service (such as military or public service).
-
B.
residenceAfterCareer
Indicates the place where an individual lives or settles after the conclusion of their professional career.
-
C.
laterResidenceShiftOf
chosen
Indicates that one residence shift event occurs chronologically after another residence shift event for the same entity.
-
D.
otherResidence
Indicates that an entity has an additional or alternative place of residence beyond its primary home.
-
E.
residence
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other entity.
- F. None of above.
Provenance (3 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:31 p.m.