Triple
T14391239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 231st Street (IRT Broadway–Seventh Avenue Line) |
E356846
|
entity |
| Predicate | hasAccessibleConnection |
P114063
|
FINISHED |
| Object | stairways |
—
|
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: stairways | Statement: [231st Street (IRT Broadway–Seventh Avenue Line), hasAccessibleConnection, stairways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessibleConnection Context triple: [231st Street (IRT Broadway–Seventh Avenue Line), hasAccessibleConnection, stairways]
-
A.
hasConnection
Indicates that there exists a link, association, or relationship between two entities.
-
B.
hasAccessMethod
Indicates that one entity uses or is associated with a particular method or mechanism for accessing another entity or resource.
-
C.
isAccessible
Indicates that one entity can be reached, used, or entered by another entity without obstruction or restriction.
-
D.
hasModeConnection
Indicates a relationship where one entity is linked to another through a specific mode, method, or type of connection.
-
E.
areAccessibleAt
Indicates that certain entities can be reached, used, or entered at a specified location, time, or context.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de902b9acc8190817ffa848a76a880 |
completed | April 14, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e08b6c08190bb4c929deab236a6 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:16 a.m.