Triple
T572992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C train |
E13701
|
entity |
| Predicate | routeLetter |
P16165
|
FINISHED |
| Object | C |
—
|
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: C | Statement: [C train, routeLetter, C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeLetter Context triple: [C train, routeLetter, C]
-
A.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
-
B.
hasLetterBy
Indicates that an entity possesses or is associated with a letter authored or sent by another entity.
-
C.
routeNumber
Indicates the specific identifying number assigned to a route within a transportation or delivery network.
-
D.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
-
E.
routeCategory
Indicates the classification or type assigned to a route within a transportation or path network.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b4ae0988190bdd0ad428b784d85 |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c4969c819080375d08f9eec50c |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a498dd579081908e02368a4c5efc8c |
completed | March 1, 2026, 7:51 p.m. |
Created at: March 1, 2026, 7:33 p.m.