Triple
T30080794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold (Mexico) |
E764452
|
entity |
| Predicate | matchRules |
P6249
|
FINISHED |
| Object | lucha libre rules |
—
|
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: lucha libre rules | Statement: [Gold (Mexico), matchRules, lucha libre rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchRules Context triple: [Gold (Mexico), matchRules, lucha libre rules]
-
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.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
-
D.
usesRulesFrom
chosen
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
-
E.
matchTypes
Indicates that two or more entities share the same type or category according to a specified classification.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d691a948190afa7fb19ae7d4ac5 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:03 p.m.