Triple
T20965961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carris bus lines |
E516366
|
entity |
| Predicate | serviceProviderFor |
P51827
|
FINISHED |
| Object | Lisbon residents |
—
|
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: Lisbon residents | Statement: [Carris bus lines, serviceProviderFor, Lisbon residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceProviderFor Context triple: [Carris bus lines, serviceProviderFor, Lisbon residents]
-
A.
serviceProviderType
Indicates the category or kind of service provider associated with an entity or transaction.
-
B.
serviceFor
Indicates that one entity provides a service or performs functions on behalf of another entity.
-
C.
providerOf
chosen
Indicates that one entity supplies, furnishes, or makes available a good, service, or resource to another entity.
-
D.
hasServiceProvider
Indicates that an entity is associated with or supported by a specific service provider.
-
E.
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.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb72ef4c8190bebdd2cef3c2148c |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:33 p.m.