Triple
T9023171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vikes |
E215976
|
entity |
| Predicate | establishedAsNickname |
P48126
|
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: [Vikes, establishedAsNickname, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsNickname Context triple: [Vikes, establishedAsNickname, 20th century]
-
A.
isOfficialNicknameOf
Indicates that one name is the formally recognized nickname or informal moniker used to refer to another entity.
-
B.
usedAsNicknameSince
chosen
Indicates that one entity has been used as a nickname for another entity starting from a specified point in time.
-
C.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
D.
stageNickname
Indicates that one entity is the stage name or performance nickname used by another entity.
-
E.
hasAffectionateNicknameFor
Indicates that one entity uses or assigns a fond, affectionate, or endearing nickname to another entity.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7a770081908dfe3ce3374a04ba |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.