Triple
T8581669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astoria–Ditmars Boulevard |
E203195
|
entity |
| Predicate | hasDirectionRole |
P43891
|
FINISHED |
| Object | northern terminal |
—
|
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: northern terminal | Statement: [Astoria–Ditmars Boulevard, hasDirectionRole, northern terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionRole Context triple: [Astoria–Ditmars Boulevard, hasDirectionRole, northern terminal]
-
A.
directionalRole
chosen
Indicates a role or function defined in terms of a direction or orientation relative to another entity or reference frame.
-
B.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
C.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
-
D.
hasDirectionReference
Indicates that one entity specifies or points to a directional orientation or reference frame for another entity.
-
E.
associatedWithDirection
Indicates that something has a relationship to, or is characterized by, a particular spatial or directional orientation.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbeb1bbbd8819082670286a711826d |
completed | March 31, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69cbd11b13108190b07f8f161425a585 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:22 p.m.