Triple
T34804035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 257 |
E1003299
|
entity |
| Predicate | followingEvent |
P165425
|
FINISHED |
| Object | UFC Fight Night: Overeem vs. Volkov |
—
|
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: UFC Fight Night: Overeem vs. Volkov | Statement: [UFC 257, followingEvent, UFC Fight Night: Overeem vs. Volkov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followingEvent Context triple: [UFC 257, followingEvent, UFC Fight Night: Overeem vs. Volkov]
-
A.
laterActivity
Indicates that one activity occurs after another in time, establishing a temporal ordering between them.
-
B.
eventLeadingTo
Indicates a causal relationship where one event brings about, triggers, or results in the occurrence of another event.
-
C.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
D.
eventFollowedBy
chosen
Indicates that one event occurs after and in sequence with another event.
-
E.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: May 3, 2026, 3:59 p.m.