Triple
T1267757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Short Line bus service |
E15639
|
entity |
| Predicate | hasServiceCategory |
P849
|
FINISHED |
| Object | scheduled bus 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: scheduled bus service | Statement: [Short Line bus service, hasServiceCategory, scheduled bus service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceCategory Context triple: [Short Line bus service, hasServiceCategory, scheduled bus service]
-
A.
hasServiceType
chosen
Indicates that an entity is associated with or categorized by a particular type of service.
-
B.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
C.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
D.
hasSeparateSupportingCategory
Indicates that an entity is associated with an additional, distinct category used specifically for supporting or auxiliary classification purposes separate from its primary category.
-
E.
hasServiceClass
Indicates that an entity is associated with, or categorized under, a particular class or type of service.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c0396e048190b4e2d7aab19268b3 |
completed | March 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.