Triple
T5786746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red route network |
E128285
|
entity |
| Predicate | includesMarking |
P32310
|
FINISHED |
| Object | single red line |
—
|
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: single red line | Statement: [Red route network, includesMarking, single red line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMarking Context triple: [Red route network, includesMarking, single red line]
-
A.
mayHaveMarkings
Indicates that an entity is permitted or able to possess certain markings or distinguishing signs.
-
B.
usedMark
Indicates that one entity has employed or applied a particular mark, symbol, or indicator in some context or action.
-
C.
usedReportingMarks
Indicates that an entity employed specific railroad reporting marks to identify rolling stock or operations.
-
D.
reportedMarks
Indicates that an entity has formally communicated or submitted the marks/grades of another entity (such as a student or assessment) to a relevant party or system.
-
E.
distinctiveMarking
chosen
Indicates that one entity bears a unique or distinguishing visual feature or pattern that sets it apart from others.
- 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a1c29d48190af36cc855bb491dd |
completed | March 22, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.