Triple
T18461004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flag of Liechtenstein |
E451033
|
entity |
| Predicate | officiallyInUseSince |
P20170
|
FINISHED |
| Object | 24 June 1937 |
—
|
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: 24 June 1937 | Statement: [flag of Liechtenstein, officiallyInUseSince, 24 June 1937]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officiallyInUseSince Context triple: [flag of Liechtenstein, officiallyInUseSince, 24 June 1937]
-
A.
developedSince
Indicates that something has been created, expanded, or advanced starting from a specified point in time and continuing thereafter.
-
B.
firstUsedOn
chosen
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
C.
firstWidelyUsedDuring
Indicates that something (such as a concept, technology, or practice) came into its first period of broad or widespread use during a specified time or era.
-
D.
currentOfficialNameSince
Indicates the date or time from which an entity has borne its current official name.
-
E.
conventionAdoptedAt
Indicates that a convention was formally adopted or agreed upon at a specific event, meeting, or location.
- 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.