Triple
T30220723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 28th Street (IRT Broadway–Seventh Avenue Line) |
E768335
|
entity |
| Predicate | hasAdjacentLineService |
P148252
|
FINISHED |
| Object | none (no express tracks) |
—
|
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: none (no express tracks) | Statement: [28th Street (IRT Broadway–Seventh Avenue Line), hasAdjacentLineService, none (no express tracks)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentLineService Context triple: [28th Street (IRT Broadway–Seventh Avenue Line), hasAdjacentLineService, none (no express tracks)]
-
A.
hasAdjacentStationOnLine1
Indicates that one station is directly next to another station along Line 1 in the network.
-
B.
adjacentLine
Indicates that one line is directly next to another line, sharing a common boundary or position without overlapping.
-
C.
hasAdjacentRailService
chosen
Indicates that one location has rail service situated directly next to or immediately bordering it.
-
D.
hasAdjacentStationOnLine4
Indicates that one station is directly next to another station along transit line 4.
-
E.
hasNearbyStateLine
Indicates that one location is situated close to the boundary line of a neighboring state.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 29, 2026, 7:35 p.m.