Triple
T37953059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luxembourg national public transport system |
E946792
|
entity |
| Predicate | serviceClassNotFree |
P5621
|
FINISHED |
| Object | first class rail |
—
|
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: first class rail | Statement: [Luxembourg national public transport system, serviceClassNotFree, first class rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceClassNotFree Context triple: [Luxembourg national public transport system, serviceClassNotFree, first class rail]
-
A.
isFreeToUse
Indicates that something can be used without cost, restriction, or required permission.
-
B.
serviceClass
chosen
Indicates the classification or category of service associated with or provided by an entity in the relationship.
-
C.
serviceClassAccess
Indicates that one entity is permitted to use or interact with a particular class or category of service provided by another entity.
-
D.
serviceUse
Indicates that one entity makes use of, accesses, or consumes a service provided by another entity.
-
E.
serviceAvailability
Indicates whether a particular service is accessible and operational for use during a given time or under specified conditions.
- 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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 3, 2026, 4:20 p.m.