Triple
T18461028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flag of Liechtenstein |
E451033
|
entity |
| Predicate | previousDesignInUseSince |
P123192
|
FINISHED |
| Object | 1921 |
—
|
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: 1921 | Statement: [flag of Liechtenstein, previousDesignInUseSince, 1921]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousDesignInUseSince Context triple: [flag of Liechtenstein, previousDesignInUseSince, 1921]
-
A.
currentDesignInForceSince
Indicates the date or point in time from which the current design has been officially in effect or valid.
-
B.
previousDesignFeature
Indicates that one design feature precedes another in a sequence or earlier version of a design.
-
C.
predecessorDesign
chosen
Indicates that one design serves as the predecessor or earlier version in relation to another design.
-
D.
hasDesignPeriod
Indicates that something was created, planned, or developed during a specified historical or stylistic design period.
-
E.
currentDesign
Indicates that an entity is the presently active or most up-to-date design associated with another entity or context.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a7fd9e081909bdf5c4aec2ba08d |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:33 a.m.