Triple
T1294267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IND Fulton Street Line (subway portion) |
E27616
|
entity |
| Predicate | usesSignage |
P5950
|
FINISHED |
| Object | A route bullet |
—
|
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: A route bullet | Statement: [IND Fulton Street Line (subway portion), usesSignage, A route bullet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSignage Context triple: [IND Fulton Street Line (subway portion), usesSignage, A route bullet]
-
A.
hasSignage
chosen
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
-
B.
hasSignageName
Indicates that an entity has a specific name or label as it appears on its physical signage.
-
C.
signageStandard
Indicates that something conforms to, follows, or specifies a particular standard or convention for signage.
-
D.
usesSignaling
Indicates that one entity communicates or coordinates with another by emitting, transmitting, or interpreting signals.
-
E.
insigniaUsedFor
Indicates that a particular insignia is employed or designated for a specific purpose, function, or use.
- 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c3bb3a9c81909db2ad91defd87b6 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bee64d908190b6a9bb479959d523 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.