Triple
T8409534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MGM Grand |
E198585
|
entity |
| Predicate | hasSignificantEventType |
P51476
|
FINISHED |
| Object | boxing matches |
—
|
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: boxing matches | Statement: [MGM Grand, hasSignificantEventType, boxing matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignificantEventType Context triple: [MGM Grand, hasSignificantEventType, boxing matches]
-
A.
hasSignificantActivity
Indicates that an entity exhibits a notable level or intensity of activity, performance, or operation relative to a defined threshold or context.
-
B.
hasEventType
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
C.
significantEventType
chosen
Indicates the specific category or kind of major or noteworthy event associated with an entity or situation.
-
D.
hasSignatureEvent
Indicates that an entity is associated with a distinctive or defining event that characterizes or highlights it.
-
E.
hasSignificant
Indicates that one entity possesses or exhibits a level of importance, impact, or relevance that is notably large or meaningful in relation to another entity or context.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb8317045c8190b69cc99854b633be |
completed | March 31, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:05 p.m.