Triple
T30080809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold (Mexico) |
E764452
|
entity |
| Predicate | titleRepresentation |
P30784
|
FINISHED |
| Object | championship belt |
—
|
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: championship belt | Statement: [Gold (Mexico), titleRepresentation, championship belt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleRepresentation Context triple: [Gold (Mexico), titleRepresentation, championship belt]
-
A.
titleRepresents
chosen
Indicates that a given title stands for, denotes, or symbolizes a particular concept, role, work, or entity.
-
B.
titleOrRole
Indicates that one entity serves as the title, position, or role held or described by another entity.
-
C.
nameRepresents
Indicates that a given name stands for, denotes, or is used to identify a particular entity.
-
D.
titleAffirms
Indicates that a title explicitly asserts, confirms, or supports the truth or validity of a particular claim, idea, or relationship.
-
E.
titleHolderDesignation
Indicates the specific role or designation held by the current holder of a particular title or position.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: April 29, 2026, 7:03 p.m.