Triple
T26967812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copa de la Liga |
E679219
|
entity |
| Predicate | participatingLevel |
P168584
|
FINISHED |
| Object | La Liga |
—
|
NE NERFINISHED |
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: La Liga | Statement: [Copa de la Liga, participatingLevel, La Liga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participatingLevel Context triple: [Copa de la Liga, participatingLevel, La Liga]
-
A.
participation
Indicates that an entity takes part in, contributes to, or is involved in a shared activity, event, or process with others.
-
B.
participationStatus
Indicates the current state or condition of an entity’s involvement in an event, activity, or process (e.g., planned, active, completed, or cancelled participation).
-
C.
engagementLevel
Indicates the degree or intensity of involvement, interest, or participation one entity has in relation to another entity, activity, or context.
-
D.
participationModel
Indicates how entities are involved in or contribute to an activity, process, or interaction.
-
E.
participationIncludes
Indicates that a broader participation instance encompasses or contains a more specific participation instance as part of it.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 27, 2026, 6:37 a.m.