Triple
T35808801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RKO |
E1035172
|
entity |
| Predicate | usedAsFinishIn |
P185082
|
FINISHED |
| Object | WWE Championship matches |
—
|
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: WWE Championship matches | Statement: [RKO, usedAsFinishIn, WWE Championship matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsFinishIn Context triple: [RKO, usedAsFinishIn, WWE Championship matches]
-
A.
usesFinishType
chosen
Indicates that one entity employs or is associated with a particular type of finish or finishing method in relation to another entity.
-
B.
typicalFinish
Indicates that an action, process, or event commonly or characteristically ends with a particular outcome or state.
-
C.
finishingMethod
Indicates the technique or process used to complete or finalize an object, task, or work.
-
D.
decorativeFinish
Indicates that one entity serves as an ornamental or aesthetic surface treatment applied to another entity.
-
E.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
Created at: May 3, 2026, 4:06 p.m.