Triple
T26479484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 168th Street and Broadway |
E664633
|
entity |
| Predicate | hasEmergencyAccessRole |
P98808
|
FINISHED |
| Object | major access point to area hospitals |
—
|
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: major access point to area hospitals | Statement: [168th Street and Broadway, hasEmergencyAccessRole, major access point to area hospitals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmergencyAccessRole Context triple: [168th Street and Broadway, hasEmergencyAccessRole, major access point to area hospitals]
-
A.
hasPrimaryAccessRole
Indicates that an entity is assigned the main or most authoritative access role governing its permissions or privileges.
-
B.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
C.
hasSafetyRole
Indicates that an entity holds a responsibility or function related to safety within a given context or system.
-
D.
hasNearbyAccess
chosen
Indicates that one entity has convenient, close-proximity access to another resource, service, or location.
-
E.
hasProtectedAreaAccess
Indicates that an entity is permitted to enter, use, or otherwise access a designated protected area under defined conditions.
- 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 12:26 a.m.