Triple
T8201502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Q (via Sixth Avenue, historical) |
E191584
|
entity |
| Predicate | usedServiceDesignation |
P38013
|
FINISHED |
| Object | Q |
—
|
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: Q | Statement: [Q (via Sixth Avenue, historical), usedServiceDesignation, Q]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedServiceDesignation Context triple: [Q (via Sixth Avenue, historical), usedServiceDesignation, Q]
-
A.
usesServiceDesignation
chosen
Indicates that one entity adopts or applies a particular service designation associated with another entity or offering.
-
B.
usedForService
Indicates that one entity is employed, utilized, or designated to perform, support, or provide a particular service for another entity.
-
C.
designationUsedFor
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
-
D.
usedAsSelfDesignation
Indicates that an entity is used by a person or group as a term to refer to or identify themselves.
-
E.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with 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_69ca82c7f3e08190857bf1fc63b2a10c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5df6e7548190846a1afd62ec6d0a |
completed | March 31, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:43 p.m.