Triple
T11842100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Battle of the Ages |
E281675
|
entity |
| Predicate | mainEventOf |
P49138
|
FINISHED |
| Object | 1991 Trump Plaza boxing card |
—
|
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: 1991 Trump Plaza boxing card | Statement: [The Battle of the Ages, mainEventOf, 1991 Trump Plaza boxing card]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainEventOf Context triple: [The Battle of the Ages, mainEventOf, 1991 Trump Plaza boxing card]
-
A.
mainEventFor
chosen
Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
-
B.
mainEvents
Indicates that the referenced entities are the primary or most significant events within a given context, sequence, or narrative.
-
C.
mainEventCity
Indicates the city in which the primary or main event takes place.
-
D.
mainEventStipulation
Indicates that a specified condition, requirement, or rule must be satisfied for the main event or primary occurrence in a given context.
-
E.
eventName
Indicates the specific label or title assigned to identify an event within a system 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.