Triple
T11043423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwest 36th Street |
E261075
|
entity |
| Predicate | hasDirectionalPrefix |
P65355
|
FINISHED |
| Object | Northwest |
—
|
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: Northwest | Statement: [Northwest 36th Street, hasDirectionalPrefix, Northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionalPrefix Context triple: [Northwest 36th Street, hasDirectionalPrefix, Northwest]
-
A.
hasDirectionalSuffix
Indicates that something is associated with or marked by a suffix expressing direction or orientation.
-
B.
hasDirectionReference
chosen
Indicates that one entity specifies or points to a directional orientation or reference frame for another entity.
-
C.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
-
D.
hasDirectionPatterns
Indicates that one entity exhibits or is associated with specific directional patterns in its behavior, structure, or configuration relative to another entity or context.
-
E.
hasPrepositionalPrefix
Indicates that one entity functions as a prepositional prefix attached to or modifying another entity.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7982d42bc81908ac10f54a7b43fb7 |
completed | April 9, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.