Triple
T38334000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Henry |
E1037900
|
entity |
| Predicate | roleAtAEW |
P131400
|
FINISHED |
| Object | commentator |
—
|
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: commentator | Statement: [Mark Henry, roleAtAEW, commentator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtAEW Context triple: [Mark Henry, roleAtAEW, commentator]
-
A.
wrestlingRole
chosen
Indicates the specific capacity or function an individual performs within a wrestling context, such as competitor, referee, coach, or other defined role.
-
B.
roleInNWA
Indicates that an entity holds or has held a specific role or position within the organization or context referred to as NWA.
-
C.
roleInGigantomachy
Indicates the specific part or function an entity played in the mythological conflict known as the Gigantomachy.
-
D.
introducedAsAEW&C
Indicates that an entity was introduced or entered into service specifically in the role of an Airborne Early Warning and Control (AEW&C) platform.
-
E.
wrestlingAlignment
Indicates the character or moral role a wrestler portrays in relation to others, such as hero, villain, or neutral, within a wrestling storyline 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:30 p.m.