Triple
T16602162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iannis |
E403355
|
entity |
| Predicate | centuryOfNotableBearerActivity |
P84738
|
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: [Iannis, centuryOfNotableBearerActivity, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centuryOfNotableBearerActivity Context triple: [Iannis, centuryOfNotableBearerActivity, 20th century]
-
A.
notableFromCentury
Indicates that an entity is notably associated with, or best known from, a particular century.
-
B.
hasNotableBearerCentury
chosen
Indicates that an entity has at least one notable bearer whose period of notability falls within the specified century.
-
C.
centuryCelebrated
Indicates that a particular century is being honored, commemorated, or formally celebrated in some way.
-
D.
associatedWithCenturyOfNameBearer
Indicates that an entity is linked to the historical century in which the person (name bearer) associated with it lived or is primarily known.
-
E.
activeInCentury
Indicates that an entity was active, influential, or operational during a specified century.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d770a048190be42180b03efba0b |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.