Triple
T15278855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple 19: Tatsueji |
E365213
|
entity |
| Predicate | sequenceNumberOnRoute |
P70742
|
FINISHED |
| Object | 19 |
—
|
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: 19 | Statement: [Temple 19: Tatsueji, sequenceNumberOnRoute, 19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sequenceNumberOnRoute Context triple: [Temple 19: Tatsueji, sequenceNumberOnRoute, 19]
-
A.
routeNumber
Indicates the specific identifying number assigned to a route within a transportation or delivery network.
-
B.
trailNumber
Indicates that an entity is associated with a specific trail identifier or route number within a trail system.
-
C.
parentRouteNumber
Indicates that one route is the immediate higher-level or containing route from which another route is derived or subordinated.
-
D.
sequenceID
chosen
Indicates that an entity is associated with a specific position or identifier within an ordered sequence.
-
E.
routeNumberSignedAs
Indicates that a route is officially signed or labeled with a particular route number on physical or digital signage.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00e504d8c8190ad6c565a31d1a9bd |
completed | April 15, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.