Triple
T9226029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMLL Homenaje a Dos Leyendas |
E221683
|
entity |
| Predicate | hasMatchCardType |
P87680
|
FINISHED |
| Object | multiple featured matches |
—
|
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: multiple featured matches | Statement: [CMLL Homenaje a Dos Leyendas, hasMatchCardType, multiple featured matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMatchCardType Context triple: [CMLL Homenaje a Dos Leyendas, hasMatchCardType, multiple featured matches]
-
A.
cardType
Indicates the classification or category assigned to a card within a given system or context.
-
B.
cardFormat
Indicates the specific layout or structural style in which a card or card-like item is presented or encoded.
-
C.
hasCardNumber
Indicates that an entity is associated with, or assigned, a specific card number.
-
D.
compatibleICCardBrand
Indicates that one entity (such as a device or system) supports and can properly operate with IC cards of the specified brand.
-
E.
cardFunction
Indicates that one entity serves as the functional role, capability, or purpose associated with a card-related entity in a system.
- F. None of above. chosen
Provenance (4 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_69ca83ec8db08190a9110df8232885d2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda9dbd1481909f35a4bee8e0b450 |
completed | April 1, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:28 p.m.