Triple
T36995353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Barcelona supporters |
E915213
|
entity |
| Predicate | attendMatchType |
P186880
|
FINISHED |
| Object | El Clásico |
—
|
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: El Clásico | Statement: [FC Barcelona supporters, attendMatchType, El Clásico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attendMatchType Context triple: [FC Barcelona supporters, attendMatchType, El Clásico]
-
A.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
B.
conferenceMatchupType
Indicates the type or category of matchup between entities within a conference context (e.g., intra-conference vs. inter-conference).
-
C.
featuredMatchType
Indicates the specific category or kind of match that is highlighted or given special prominence.
-
D.
matchType
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
E.
homeMatchType
Indicates the type or category of match in which an entity is designated as the home side.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb154b5f8c819089103b41f51a1639 |
completed | May 6, 2026, 10:17 a.m. |
Created at: May 3, 2026, 4:14 p.m.