Triple
T35809063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RK-Bro |
E1035178
|
entity |
| Predicate | hasFinisherName |
P201369
|
FINISHED |
| Object | RKO (by Randy Orton) |
—
|
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: RKO (by Randy Orton) | Statement: [RK-Bro, hasFinisherName, RKO (by Randy Orton)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinisherName Context triple: [RK-Bro, hasFinisherName, RKO (by Randy Orton)]
-
A.
hasFinisherNameMeaning
Indicates that an entity’s finishing move is associated with a specific meaning or interpretation of its name.
-
B.
hasCommonFinish
Indicates that two or more entities share the same type or style of finish (e.g., surface treatment, coating, or final appearance).
-
C.
finisherFor
Indicates that one entity serves as the concluding or final component, action, or step for another entity.
-
D.
hasCombinerName
Indicates that an entity is associated with a specific name used to identify its combiner or combining mechanism.
-
E.
hasNameSuffix
Indicates that an entity’s name includes a specific suffix or ending component.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffed8912488190baa05f572e5b1b89 |
completed | May 10, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69ffed12a76c8190ad85c6ac869c72e9 |
completed | May 10, 2026, 2:27 a.m. |
| PDg | Predicate description generation | batch_69ffed884b908190b12422c790b1525e |
completed | May 10, 2026, 2:29 a.m. |
Created at: May 3, 2026, 4:06 p.m.