Triple
T35600624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antônio Rodrigo Nogueira |
E1028753
|
entity |
| Predicate | promotionRole |
P13067
|
FINISHED |
| Object | UFC ambassador in Brazil |
—
|
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: UFC ambassador in Brazil | Statement: [Antônio Rodrigo Nogueira, promotionRole, UFC ambassador in Brazil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionRole Context triple: [Antônio Rodrigo Nogueira, promotionRole, UFC ambassador in Brazil]
-
A.
promotionalRole
chosen
Indicates that an entity serves in a capacity focused on promoting, advertising, or publicizing another entity, product, or activity.
-
B.
profileRole
Indicates the specific role or function an entity holds within a given profile or contextual configuration.
-
C.
providedRole
Indicates that one entity has assigned or supplied a specific role or function to another entity.
-
D.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
E.
promotionBy
Indicates that one entity advances, elevates, or publicizes another entity, typically by increasing its status, visibility, or level.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:05 p.m.