Triple
T26958917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 36th Street |
E678981
|
entity |
| Predicate | hasServiceHeader |
P187563
|
FINISHED |
| Object | D |
—
|
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: D | Statement: [36th Street, hasServiceHeader, D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceHeader Context triple: [36th Street, hasServiceHeader, D]
-
A.
hasServiceClass
Indicates that an entity is associated with, or categorized under, a particular class or type of service.
-
B.
hasServiceName
Indicates that an entity is associated with or identified by a specific service name.
-
C.
hasServiceModule
Indicates that an entity is equipped with, or associated with, a specific service module that provides supporting or auxiliary functions.
-
D.
hasServiceStructure
Indicates that one entity provides, contains, or is associated with a particular service-related structure or organizational framework for delivering a service.
-
E.
hasKeyService
Indicates that one entity provides or is associated with a primary or essential service for another entity.
- F. None of above. chosen
Provenance (4 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb6fdab95c81909acff3c6a2359787 |
completed | May 6, 2026, 4:44 p.m. |
Created at: April 27, 2026, 6:29 a.m.