Triple
T37632601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McGillicutter |
E936391
|
entity |
| Predicate | performerLaterRingName |
P68993
|
FINISHED |
| Object | Curtis Axel |
—
|
NE NERFINISHED |
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: Curtis Axel | Statement: [McGillicutter, performerLaterRingName, Curtis Axel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerLaterRingName Context triple: [McGillicutter, performerLaterRingName, Curtis Axel]
-
A.
laterPerformerName
chosen
Indicates that an entity’s name refers to a performer who took on a role or performance at a later time than another performer associated with the same context or work.
-
B.
headlinerRingName
Indicates the professional or stage name under which a headlining performer is billed or promoted.
-
C.
originalRingName
Indicates the name originally used for a ring before any later changes or renamings.
-
D.
mainPerformerCurrentName
Indicates that the referenced name is the current official or primary name of the main performer associated with an event or work.
-
E.
performerCharacterName
Indicates that a performer is associated with or portrays a specific character name in a performance or work.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
Created at: May 3, 2026, 4:18 p.m.