Triple
T11056014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clásico Regio |
E261377
|
entity |
| Predicate | hasMatchContext |
P35407
|
FINISHED |
| Object | league 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: league matches | Statement: [Clásico Regio, hasMatchContext, league matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMatchContext Context triple: [Clásico Regio, hasMatchContext, league matches]
-
A.
matchContext
chosen
Indicates that two or more entities are related within the same situational, conversational, or environmental setting that frames or influences their interaction.
-
B.
hasMatchFormat
Indicates that something (such as a game, event, or competition) is conducted according to a specified match format or structure.
-
C.
hasMaterialContext
Indicates that something is associated with, influenced by, or situated within a particular physical or material context.
-
D.
hasCanonicalContext
Indicates that something is associated with its primary, standard, or officially recognized contextual setting or framework.
-
E.
hasCodeContext
Indicates that an entity is associated with or occurs within a particular programming or code-related context.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798a152b4819095b74a8996346077 |
completed | April 9, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.