Triple
T7214873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Lijn bus lines |
E149505
|
entity |
| Predicate | hasMobileAppSupport |
P14571
|
FINISHED |
| Object | De Lijn app |
—
|
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: De Lijn app | Statement: [De Lijn bus lines, hasMobileAppSupport, De Lijn app]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMobileAppSupport Context triple: [De Lijn bus lines, hasMobileAppSupport, De Lijn app]
-
A.
hasApp
chosen
Indicates that an entity possesses, provides, or is associated with a particular application.
-
B.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
C.
hasCellularComponent
Indicates that an entity possesses, includes, or is associated with a specific cellular component as part of its structure or organization.
-
D.
tieneSoporte
Indicates that one entity provides support, backing, or a supporting structure for another entity.
-
E.
hasCellService
Indicates that a location, device, or area is within range of a cellular network and can access mobile phone or data services.
- 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.