Triple
T11790690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chemins de Fer Luxembourgeois |
E280378
|
entity |
| Predicate | UICCompanyCode |
P101595
|
FINISHED |
| Object | 1182 |
—
|
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: 1182 | Statement: [Chemins de Fer Luxembourgeois, UICCompanyCode, 1182]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UICCompanyCode Context triple: [Chemins de Fer Luxembourgeois, UICCompanyCode, 1182]
-
A.
underlyingCompanyIATA
Indicates that an entity is associated with an underlying company identified by a specific IATA (International Air Transport Association) code.
-
B.
operatingCompanyAbbreviation
Indicates that the object is an abbreviated or shortened form of the name of the company that operates the subject.
-
C.
underlyingCompanyAbbreviation
Indicates that one entity is the abbreviated or short-form name used to refer to an underlying company represented by another entity.
-
D.
IATAcode
Indicates the three-letter IATA airport or airline code assigned to the entity.
-
E.
originatingCompany
Indicates the company from which something (such as a product, document, transaction, or request) originally comes or is issued.
- F. None of above. chosen
Provenance (4 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a588d2c881909783c2d678c2a474 |
completed | April 10, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:42 p.m.