Triple
T4604327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manhattan Railway elevated lines |
E100392
|
entity |
| Predicate | finalClosure |
P56128
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Manhattan Railway elevated lines, finalClosure, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalClosure Context triple: [Manhattan Railway elevated lines, finalClosure, 1950s]
-
A.
closureCompleted
chosen
Indicates that a previously initiated closure process or shutdown has been fully and successfully completed.
-
B.
closureProcess
Indicates the procedure or set of actions carried out to formally conclude, finalize, or terminate an ongoing activity, case, or process.
-
C.
closure
Indicates that an entity is closed or not accessible/available for use, entry, or interaction.
-
D.
closureProgram
Indicates that an entity is a program or plan specifically associated with the closure or shutdown of another entity or operation.
-
E.
finalStep
Indicates that an action or state represents the last step or concluding stage in a process or sequence.
- 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_69bd43cce1e08190a07d53af6a9b6c24 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5999f9c88190a43309573df61159 |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.