Triple
T22049089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adidas Brazuca |
E544835
|
entity |
| Predicate | nameChosenBy |
P146386
|
FINISHED |
| Object | public vote |
—
|
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: public vote | Statement: [Adidas Brazuca, nameChosenBy, public vote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameChosenBy Context triple: [Adidas Brazuca, nameChosenBy, public vote]
-
A.
nameChosenToBe
Indicates that an entity has been given or selected to have a particular name.
-
B.
nameProposedBy
Indicates that one entity is the proposer or originator of a particular name assigned to another entity.
-
C.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
-
D.
nameElementIn
Indicates that an entity is (or contains) a specific name element within a larger naming structure or system.
-
E.
nameProposedIn
Indicates that a particular name was suggested or put forward within a specific proposal, context, or event.
- F. None of above. chosen
Provenance (4 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1283191e48190b4ddc84138243327 |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:26 p.m.