Triple
T9398836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMLL Juicio Final |
E226414
|
entity |
| Predicate | rulesStyle |
P16452
|
FINISHED |
| Object | Mexican 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: Mexican lucha libre rules | Statement: [CMLL Juicio Final, rulesStyle, Mexican lucha libre rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulesStyle Context triple: [CMLL Juicio Final, rulesStyle, Mexican lucha libre rules]
-
A.
styleOfRule
chosen
Indicates the stylistic or formatting convention that a particular rule follows or is expressed in.
-
B.
styleRestriction
Indicates a constraint or limitation imposed on the manner, form, or stylistic way in which something may be expressed, presented, or performed.
-
C.
styleLanguage
Indicates a relationship where one entity specifies the language or linguistic style in which another entity is expressed, formatted, or presented.
-
D.
styleRange
Indicates that a particular style or formatting is applied over a specified span or range within a larger structure.
-
E.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51556fc08190b8ff8190a1485a3a |
completed | April 1, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:46 p.m.