Triple
T28074107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Devils |
E709485
|
entity |
| Predicate | nativeNickname |
P11214
|
FINISHED |
| Object | Rode Duivels |
—
|
NE NERFINISHED |
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: Rode Duivels | Statement: [Red Devils, nativeNickname, Rode Duivels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeNickname Context triple: [Red Devils, nativeNickname, Rode Duivels]
-
A.
localNickname
chosen
Indicates that an entity is known by a particular nickname within a specific local or regional context.
-
B.
unofficialNickname
Indicates that one entity is informally or colloquially known by a non-official nickname represented by the other entity.
-
C.
isOfficialNicknameOf
Indicates that one name is the formally recognized nickname or informal moniker used to refer to another entity.
-
D.
usesNicknameOf
Indicates that one entity refers to another entity by a nickname derived from or associated with that other entity’s name.
-
E.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:47 p.m.