Triple
T30956659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beijing 2008 Olympic Torch Relay |
E788693
|
entity |
| Predicate | domesticLegIn |
P170839
|
FINISHED |
| Object | China |
—
|
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: China | Statement: [Beijing 2008 Olympic Torch Relay, domesticLegIn, China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domesticLegIn Context triple: [Beijing 2008 Olympic Torch Relay, domesticLegIn, China]
-
A.
firstLeg
Indicates that one entity represents the initial segment or starting portion of a multi-part journey, sequence, or process involving another entity.
-
B.
isDomestic
Indicates that an entity exists or is used primarily within a home or internal context rather than in a foreign or wild environment.
-
C.
triadLeg
Indicates that an entity functions as one of the three supporting legs or components in a triadic structure or system.
-
D.
domesticDoubleType
Indicates that an entity is associated with a domestic context in two distinct but related ways or categories within the same domain.
-
E.
landLegSystem
Indicates a relationship where a landing system is specifically designed for or associated with a leg-based support or landing mechanism.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:54 p.m.