Triple
T35810111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ROH Pure Wrestling Championship |
E1035205
|
entity |
| Predicate | matchRulesFeature |
P149943
|
FINISHED |
| Object | limited number of rope breaks per wrestler |
—
|
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: limited number of rope breaks per wrestler | Statement: [ROH Pure Wrestling Championship, matchRulesFeature, limited number of rope breaks per wrestler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchRulesFeature Context triple: [ROH Pure Wrestling Championship, matchRulesFeature, limited number of rope breaks per wrestler]
-
A.
typicalMatchRules
Indicates that two entities are considered a standard or default match according to predefined matching rules or criteria.
-
B.
matchOutcomeRule
Indicates the rule or condition that determines the outcome of a match between participants.
-
C.
hasRuleCharacteristic
chosen
Indicates that something possesses a specific property, feature, or attribute related to a rule or set of rules.
-
D.
usesRulesFrom
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
-
E.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over 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_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:06 p.m.