Triple
T10523122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boyata |
E248223
|
entity |
| Predicate | hasIconicStatusSince |
P2007
|
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: [Boyata, hasIconicStatusSince, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIconicStatusSince Context triple: [Boyata, hasIconicStatusSince, 20th century]
-
A.
hasIconicStatus
chosen
Indicates that an entity holds a widely recognized, emblematic, or culturally significant status within a particular domain or context.
-
B.
isIconicIn
Indicates that something is widely recognized as a defining or emblematic example within a particular context, domain, or location.
-
C.
hasAdministrativeStatusSince
Indicates that an entity has held a particular administrative status continuously from a specified point in time onward.
-
D.
hasIconicCharacter
Indicates that something is associated with a character widely recognized as emblematic or highly representative of it.
-
E.
hadSpecialStatusIn
Indicates that an entity possessed a particular special, exceptional, or non-standard status within a specified context or time period.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509e155b08190996325bf484ec55d |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:29 p.m.