Triple
T20749497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMA |
E510679
|
entity |
| Predicate | firstMajorEventYear |
P141353
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [MMA, firstMajorEventYear, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMajorEventYear Context triple: [MMA, firstMajorEventYear, 1993]
-
A.
firstMajorEventAt
Indicates that the referenced event is the earliest major event associated with the given entity, specifying when that first significant occurrence takes place.
-
B.
firstMajorInternationalEvent
Indicates that the event is the earliest significant international-level occurrence in which the entity participated or was involved.
-
C.
firstMajorRallyYear
Indicates the calendar year in which an entity held its first significant rally or major organized gathering.
-
D.
firstMajorUseYear
Indicates the calendar year in which something was first put into major or primary use.
-
E.
firstMajorRunYear
Indicates the year in which something (such as an event, production, or operation) first began its major or primary run.
- 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c228af288190a20829d45c034c24 |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:34 p.m.