Triple
T7214856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Lijn bus lines |
E149505
|
entity |
| Predicate | acceptsTicket |
P74693
|
FINISHED |
| Object | Lijnkaart |
—
|
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: Lijnkaart | Statement: [De Lijn bus lines, acceptsTicket, Lijnkaart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptsTicket Context triple: [De Lijn bus lines, acceptsTicket, Lijnkaart]
-
A.
hasTicketing
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
-
B.
ticketingCompatibleWith
Indicates that two systems, services, or components can interoperate or be used together within the same ticketing or reservation workflow without conflict.
-
C.
ticketAcceptanceArea
chosen
Indicates the geographic or operational area within which a given ticket is valid for use or accepted as proof of payment.
-
D.
hasTicketIntegration
Indicates that there is an established connection enabling ticket-related data or actions to be shared or synchronized between systems or components.
-
E.
acceptedIn
Indicates that something has been formally received, approved, or admitted into a particular context, group, or system.
- 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_69c687eca814819095abb52316b1af80 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e98ebe1c81909891b4a1c2c3a4aa |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:53 p.m.