Triple
T10941708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 46th Street–Bliss Street |
E258487
|
entity |
| Predicate | hasDirectionNames |
P75158
|
FINISHED |
| Object | Manhattan-bound |
—
|
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: Manhattan-bound | Statement: [46th Street–Bliss Street, hasDirectionNames, Manhattan-bound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionNames Context triple: [46th Street–Bliss Street, hasDirectionNames, Manhattan-bound]
-
A.
hasDirectionLabels
chosen
Indicates that a subject is associated with one or more labels specifying directions or orientations.
-
B.
hasDirectionVariant
Indicates that one entity is a directional variant or orientation-specific form of another entity.
-
C.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
-
D.
hasDirectionTitle
Indicates that an entity holds the role or position of director, as specified by a particular title.
-
E.
hasDirectionScheme
Indicates that an entity is associated with or governed by a particular scheme or system for defining directions.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770c33a7c8190b3347944f68ee431 |
completed | April 9, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69d72e816a98819096d6c10dfb88a66a |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.