Triple
T9138387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMLL Anniversary Show |
E219261
|
entity |
| Predicate | typicalMatchStyle |
P27263
|
FINISHED |
| Object | trios match |
—
|
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: trios match | Statement: [CMLL Anniversary Show, typicalMatchStyle, trios match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMatchStyle Context triple: [CMLL Anniversary Show, typicalMatchStyle, trios match]
-
A.
typicalMatchType
chosen
Indicates the usual or most common type of match or pairing that characterizes how two entities are related or aligned.
-
B.
matchType
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
C.
typicalVisualStyle
Indicates the characteristic or commonly observed visual appearance or aesthetic style associated with an entity.
-
D.
typicalAlignment
Indicates the usual or most common way in which two entities are positioned, oriented, or arranged relative to each other.
-
E.
styleTendsTo
Indicates that one style is generally inclined or likely to develop, appear, or be adopted in the direction of another style.
- 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8efe3b88190a55a15827e6817a4 |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:19 p.m.