Triple
T33105209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinsuke Nakamura |
E847169
|
entity |
| Predicate | MMARecord |
P151050
|
FINISHED |
| Object | 3–1–1 |
—
|
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: 3–1–1 | Statement: [Shinsuke Nakamura, MMARecord, 3–1–1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MMARecord Context triple: [Shinsuke Nakamura, MMARecord, 3–1–1]
-
A.
mmaRecord
chosen
Indicates a competitive mixed martial arts fight record between entities, typically summarizing wins, losses, and related bout outcomes.
-
B.
MMAOrganization
Indicates an organizational relationship where an entity functions as a mixed martial arts promotion or governing body associated with fighters, events, or titles.
-
C.
MVPRecord
Indicates that an entity holds a record for the most valuable player (MVP) distinction within a particular context, competition, or time period.
-
D.
MAMAType
Indicates a classification relationship where an entity is assigned a specific type or category within the MAMA schema or framework.
-
E.
RBIRecord
Indicates that a record exists documenting a specific instance of a run batted in (RBI) credited to a player in a baseball 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6e69e388190b2d3e90b11277232 |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:26 a.m.