Triple
T35493075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC Interim Heavyweight Championship |
E1025780
|
entity |
| Predicate | combatArea |
P183351
|
FINISHED |
| Object | octagon |
—
|
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: octagon | Statement: [UFC Interim Heavyweight Championship, combatArea, octagon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatArea Context triple: [UFC Interim Heavyweight Championship, combatArea, octagon]
-
A.
combatView
Indicates a perspective or representation of entities engaged in combat or battle-related interaction.
-
B.
combatBy
Indicates a relationship where one entity engages in combat or fighting through the agency, actions, or involvement of another entity.
-
C.
combat
Indicates that two or more entities are engaged in fighting or armed conflict with each other.
-
D.
combatIndicator
Indicates that an entity is involved in, associated with, or signaling the occurrence of combat or hostile activity.
-
E.
combatApplication
Indicates the application or use of something (such as skills, tactics, or equipment) within a combat or fighting context.
- 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_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:04 p.m.