Triple
T19191610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ninth Avenue Line |
E469851
|
entity |
| Predicate | convertedToSteamOperation |
P134808
|
FINISHED |
| Object | 1870s |
—
|
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: 1870s | Statement: [Ninth Avenue Line, convertedToSteamOperation, 1870s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedToSteamOperation Context triple: [Ninth Avenue Line, convertedToSteamOperation, 1870s]
-
A.
conversionStepOf
Indicates that one process, operation, or stage functions as a constituent step within a larger overall conversion process.
-
B.
conversionProcess
Indicates a process in which something is transformed or changed from one state, form, or representation into another.
-
C.
convertedBy
Indicates that one entity has been transformed or changed in form, state, or representation through the action or process performed by another entity.
-
D.
steamToDieselConversion
Indicates the process or relationship in which a steam-powered system, vehicle, or operation is replaced or converted to diesel power.
-
E.
convertedToGasStorage
Indicates that something has been transformed or repurposed into a facility or system used for storing gas.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f8a226dc8190a8a96960a4180298 |
completed | April 20, 2026, 9:57 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:07 p.m.