Triple
T35842806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ROH World Tag Team Championship |
E1036131
|
entity |
| Predicate | isPrimaryTagTitleOf |
P188790
|
FINISHED |
| Object | Ring of Honor |
—
|
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: Ring of Honor | Statement: [ROH World Tag Team Championship, isPrimaryTagTitleOf, Ring of Honor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryTagTitleOf Context triple: [ROH World Tag Team Championship, isPrimaryTagTitleOf, Ring of Honor]
-
A.
hasPrimaryTitle
Indicates that an entity is associated with its main or official title, distinguishing it from any alternative or secondary titles.
-
B.
isTitleFor
Indicates that one entity serves as the official title or name designation for another entity.
-
C.
isPrimaryTriosTitleOf
chosen
Indicates that a title is the main or primary title associated with a specific Trios entity.
-
D.
isPrimary
Indicates that one entity holds the main, leading, or most important role or status in relation to another entity or within a given context.
-
E.
isTitleMatchFor
Indicates that one entity’s title matches or corresponds to the title of 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 3, 2026, 4:06 p.m.