Triple
T31504890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Viernes |
E803789
|
entity |
| Predicate | typicalMatchCardLength |
P207442
|
FINISHED |
| Object | multiple matches per event |
—
|
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 matches per event | Statement: [Super Viernes, typicalMatchCardLength, multiple matches per event]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMatchCardLength Context triple: [Super Viernes, typicalMatchCardLength, multiple matches per event]
-
A.
cardLength
Indicates the length or size measurement associated with a card.
-
B.
typicalMatchType
Indicates the usual or most common type of match or pairing that characterizes how two entities are related or aligned.
-
C.
typicalMatchRules
Indicates that two entities are considered a standard or default match according to predefined matching rules or criteria.
-
D.
typicalLength
Indicates the usual or characteristic length associated with an entity or phenomenon.
-
E.
usesMatchLength
Indicates that one entity applies or enforces the same length or duration as that of a corresponding match or matching element.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 30, 2026, 9:46 p.m.