Triple
T6228801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flag of Luxembourg |
E139300
|
entity |
| Predicate | firstUseOfTricolour |
P69028
|
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: [flag of Luxembourg, firstUseOfTricolour, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUseOfTricolour Context triple: [flag of Luxembourg, firstUseOfTricolour, 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.
dayOfTheTricolour
Indicates a relationship where a specific day is designated as the Day of the Tricolour, typically commemorating or celebrating a tricolour flag or symbol.
-
C.
isVerticalTricolour
Indicates that something consists of three distinct coloured sections arranged in vertical bands.
-
D.
coatOfArmsStartUse
Indicates the point in time when a particular coat of arms first began to be used or officially adopted.
-
E.
inUseAsRoyalNavyEnsignUntil
Indicates that something served as the Royal Navy ensign up to a specified end date.
- 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_69c008afd3148190b71e9eaa60420dd1 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062d841a88190b67a8045cdaadf44 |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c965ac8190b938502fa8c74e1b |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:22 p.m.