Triple
T23821118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interborough Rapid Transit legacy lines |
E589239
|
entity |
| Predicate | historicallyIncludesLine |
P76655
|
FINISHED |
| Object | original IRT subway 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: original IRT subway line | Statement: [Interborough Rapid Transit legacy lines, historicallyIncludesLine, original IRT subway line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyIncludesLine Context triple: [Interborough Rapid Transit legacy lines, historicallyIncludesLine, original IRT subway line]
-
A.
lineHistorically
Indicates that a line or route has existed or operated during a specific historical period or context.
-
B.
includeHistoricalSee
Indicates that a relationship or reference should also encompass or display historically related "see also" connections or pointers.
-
C.
hasHistoricalText
Indicates that an entity is associated with a historical written document or record describing it or its past.
-
D.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
E.
lineHistoricallyPartOf
chosen
Indicates that a given line (such as a route, boundary, or infrastructure segment) was formerly included within or belonged to a larger line or system at some point in the past.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7af4d4481908095348fae9e54f4 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:59 p.m.