Triple
T24965931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 86th Street |
E624741
|
entity |
| Predicate | historicSystem |
P167703
|
FINISHED |
| Object | original IRT subway |
—
|
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: original IRT subway | Statement: [86th Street, historicSystem, original IRT subway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicSystem Context triple: [86th Street, historicSystem, original IRT subway]
-
A.
historicFor
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
B.
historicalPeriodOfSystematization
Indicates the historical period during which a practice, knowledge domain, or system was formally organized, codified, or systematized.
-
C.
politicalSystemHistorical
Indicates a relationship where a political system is characterized or analyzed in terms of its historical development, context, or evolution.
-
D.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
E.
historicCore
Indicates that something is part of, located within, or associated with the original historic center or oldest developed area of a place.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 18, 2026, 6 a.m.