Triple
T25527931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 7 |
E639824
|
entity |
| Predicate | directionDesignation |
P30236
|
FINISHED |
| Object | Queens-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: Queens-bound | Statement: [7, directionDesignation, Queens-bound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionDesignation Context triple: [7, directionDesignation, Queens-bound]
-
A.
directionalDesignation
chosen
Indicates a relationship where one entity is assigned or labeled with a specific directional orientation relative to another entity or reference frame.
-
B.
bdDesignation
Indicates that one entity is formally assigned or designated as having a particular role, status, or classification in relation to another entity.
-
C.
designationFor
Indicates that one entity serves as the official title, label, or role name assigned to another entity.
-
D.
mapDesignation
Indicates a formal label or identifier that is assigned to something specifically for use on a map.
-
E.
mountDesignation
Indicates that one entity is designated or assigned as the mount (e.g., riding or support animal/vehicle) for 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 21, 2026, 3:12 p.m.