Triple
T25064493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BaltimoreLink |
E627744
|
entity |
| Predicate | hasServiceSpan |
P99305
|
FINISHED |
| Object | daily 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: daily service | Statement: [BaltimoreLink, hasServiceSpan, daily service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceSpan Context triple: [BaltimoreLink, hasServiceSpan, daily service]
-
A.
hasServiceTime
chosen
Indicates that an entity is associated with a specific duration or schedule during which a service is provided.
-
B.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
C.
hasServiceProvider
Indicates that an entity is associated with or supported by a specific service provider.
-
D.
hasCounterService
Indicates that a place provides service to customers over a counter, such as ordering, paying, or receiving items at a service counter.
-
E.
hasServiceFunction
Indicates that an entity performs, provides, or is responsible for a particular service-related function or role.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 18, 2026, 6:10 a.m.