Triple
T12355654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luxembourg flag |
E294605
|
entity |
| Predicate | firstUseAsNationalSymbol |
P104732
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Luxembourg flag, firstUseAsNationalSymbol, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUseAsNationalSymbol Context triple: [Luxembourg flag, firstUseAsNationalSymbol, 19th century]
-
A.
adoptedAsNationalFlagOn
Indicates that an entity was officially chosen and put into use as a country's national flag on a specific date.
-
B.
firstUseOfTricolour
Indicates the event or situation in which a particular tricolour flag was used for the first time.
-
C.
adoptedAsEmblemBy
Indicates that something has been officially chosen and used as a symbolic emblem by a particular entity or group.
-
D.
adoptedAsNavalEnsign
Indicates that something has been officially selected and put into use as a naval ensign (a flag or emblem representing a navy).
-
E.
hasNationalSymbol
Indicates that an entity possesses or is associated with an officially recognized national symbol of a country or nation.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d942a2d6e08190a13c7ff89af09354 |
completed | April 10, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69d93ecf6b548190a394b6b56a0c1c68 |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d9429ff2bc8190b09adf8f57fad451 |
completed | April 10, 2026, 6:34 p.m. |
Created at: April 8, 2026, 9:54 p.m.