Triple
T18152941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D (New York City Subway service) |
E434552
|
entity |
| Predicate | hasServiceClassification |
P5621
|
FINISHED |
| Object | lettered service |
—
|
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: lettered service | Statement: [D (New York City Subway service), hasServiceClassification, lettered service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceClassification Context triple: [D (New York City Subway service), hasServiceClassification, lettered service]
-
A.
hasServiceClass
Indicates that an entity is associated with, or categorized under, a particular class or type of service.
-
B.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
C.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
D.
serviceClass
chosen
Indicates the classification or category of service associated with or provided by an entity in the relationship.
-
E.
usesClassificationCriteria
Indicates that one entity applies specific classification criteria to categorize, organize, or evaluate 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de39a8f481908d1752767d0aae0e |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.