Triple
T27740170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gail Kim |
E701830
|
entity |
| Predicate | roleAtImpactWrestling |
P131400
|
FINISHED |
| Object | producer |
—
|
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: producer | Statement: [Gail Kim, roleAtImpactWrestling, producer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtImpactWrestling Context triple: [Gail Kim, roleAtImpactWrestling, producer]
-
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.
roleInUFC
Indicates the specific capacity or position an entity holds within the context of the Ultimate Fighting Championship (UFC), such as fighter, referee, coach, or official.
-
C.
roleInGigantomachy
Indicates the specific part or function an entity played in the mythological conflict known as the Gigantomachy.
-
D.
wrestledWith
Indicates that one entity engaged in a physical wrestling contest or struggle with another entity.
-
E.
managedWrestler
Indicates that one entity served as the manager of another entity in a professional wrestling 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 4:10 p.m.