Triple
T8554062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NS Sprinter |
E202518
|
entity |
| Predicate | serviceCategoryWithinNS |
P5621
|
FINISHED |
| Object | Sprinter |
—
|
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: Sprinter | Statement: [NS Sprinter, serviceCategoryWithinNS, Sprinter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceCategoryWithinNS Context triple: [NS Sprinter, serviceCategoryWithinNS, Sprinter]
-
A.
publicServiceCategory
Indicates the classification or type of public service that an entity, activity, or offering belongs to.
-
B.
servicePatternOf
Indicates that one entity is the service pattern (e.g., schedule, routing, or operational configuration) that defines or characterizes how another service-related entity operates.
-
C.
hasSupportCategory
Indicates that an entity is associated with a particular type or category of support it receives or provides.
-
D.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
-
E.
serviceClass
chosen
Indicates the classification or category of service associated with or provided by an entity in the relationship.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe8894e7c8190bc0ae2ceec473ecb |
completed | March 31, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:19 p.m.