Triple
T1217899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Line (Washington Metro) |
E26147
|
entity |
| Predicate | isFirstLineOfSystem |
P25099
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Red Line (Washington Metro), isFirstLineOfSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFirstLineOfSystem Context triple: [Red Line (Washington Metro), isFirstLineOfSystem, true]
-
A.
firstLineOpened
Indicates that the first line of something (e.g., a document, file, or text block) has been opened or accessed.
-
B.
wasFirst
Indicates that one entity occurred, appeared, or held a position before another in time or sequence.
-
C.
isLinedWith
Indicates that one object or surface is covered, edged, or internally coated along its length or area with another material or layer.
-
D.
isStandardIn
Indicates that something conforms to or is officially recognized as the accepted standard within a particular context or system.
-
E.
hasLineNumber
Indicates that something is associated with a specific line number, typically denoting its position within an ordered sequence such as lines of text or code.
- 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_69a4948331fc8190b531ac9bec71c491 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be08157c8190b248bb75b922644f |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb62a7c08190a79dcb6ff72ac99b |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc6d5b7881908091e40c8695ef53 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:46 p.m.