Triple
T23152729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lëtzebuerger Fändel |
E578361
|
entity |
| Predicate | alternativeFlagRelated |
P150620
|
FINISHED |
| Object | Roude Léiw |
—
|
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: Roude Léiw | Statement: [Lëtzebuerger Fändel, alternativeFlagRelated, Roude Léiw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeFlagRelated Context triple: [Lëtzebuerger Fändel, alternativeFlagRelated, Roude Léiw]
-
A.
alternativeFlag
chosen
Indicates that something is marked or designated as an alternative option or variant relative to a primary or default choice.
-
B.
associatedWithFlag
Indicates a relationship where an entity is linked or connected to a particular flag, such as a national, organizational, or symbolic banner.
-
C.
formerFlag
Indicates that an entity previously served as a flag of another entity but no longer holds that status.
-
D.
alternativeBenefit
Indicates that one benefit serves as a substitute or replacement for another possible benefit in a given context.
-
E.
alternativeHolder
Indicates that one entity serves as an alternative or substitute holder in place of another entity.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18efaa1fc81908fb1987dbf732f46 |
completed | April 29, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.