Triple
T10363189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estelada flag |
E244185
|
entity |
| Predicate | firstUsedInCentury |
P6026
|
FINISHED |
| Object | 20th 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: 20th century | Statement: [Estelada flag, firstUsedInCentury, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUsedInCentury Context triple: [Estelada flag, firstUsedInCentury, 20th century]
-
A.
introducedInCentury
chosen
Indicates the century during which something (such as an idea, technology, practice, or entity) was first introduced or came into use.
-
B.
usedInCentury
Indicates that something (such as an object, practice, or concept) was in use during a specified century.
-
C.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
-
D.
acquiredInCentury
Indicates that one entity was acquired during a specific century represented by the other entity.
-
E.
developedSinceCentury
Indicates that something began to be developed or came into existence starting from a specified century onward.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e963a6148190822951e72590b9df |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, noon