Triple
T33732887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Broadway Street, Frankfort |
E864320
|
entity |
| Predicate | nameDirection |
P117258
|
FINISHED |
| Object | West |
—
|
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: West | Statement: [West Broadway Street, Frankfort, nameDirection, West]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameDirection Context triple: [West Broadway Street, Frankfort, nameDirection, West]
-
A.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
-
B.
geographicDirectionImpliedByName
Indicates that the name of a place or feature suggests a specific geographic direction (e.g., north, south, east, west) relative to some reference.
-
C.
latitudeDirection
Indicates the cardinal direction (north or south) associated with a given latitude value relative to the equator.
-
D.
hasDirectionInName
chosen
Indicates that the entity’s name explicitly contains a directional term (e.g., north, south, east, west, or similar).
-
E.
directionType
Indicates the specific kind or category of direction associated with a movement, orientation, or relation between entities.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 1, 2026, 1:44 a.m.