Triple
T14340796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumadaniji |
E355593
|
entity |
| Predicate | sequencePositionOnRoute |
P86484
|
FINISHED |
| Object | early stage |
—
|
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: early stage | Statement: [Kumadaniji, sequencePositionOnRoute, early stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sequencePositionOnRoute Context triple: [Kumadaniji, sequencePositionOnRoute, early stage]
-
A.
relativePositionOnCourse
Indicates the positional relationship of one participant or object relative to another along a defined course or route.
-
B.
locatedOnRouteTo
Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
-
C.
segmentPosition
chosen
Indicates the relative location or ordering of a segment within a larger sequence or structure.
-
D.
isPartOfRoute
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
E.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e87febc8190a63c668cbd0fd713 |
completed | April 14, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.