Triple
T15057787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Club de Deportes Coquimbo Unido |
E379540
|
entity |
| Predicate | hasSupporterType |
P13349
|
FINISHED |
| Object | passionate fan base |
—
|
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: passionate fan base | Statement: [Club de Deportes Coquimbo Unido, hasSupporterType, passionate fan base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupporterType Context triple: [Club de Deportes Coquimbo Unido, hasSupporterType, passionate fan base]
-
A.
hasSupporter
Indicates that one entity supports, endorses, or backs another entity.
-
B.
supporterType
chosen
Indicates the specific role or category of support a supporter provides in relation to another entity or activity.
-
C.
hasSupporterGroup
Indicates that an entity is associated with a group of supporters that backs, promotes, or advocates for it.
-
D.
supportsParticipantType
Indicates that an entity is compatible with, or designed to work with, a specified type or category of participant.
-
E.
hasSupporterOwnershipElement
Indicates that an entity includes or is associated with an ownership-related element specifically tied to a supporter.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69deda937f788190899d81bbb2084443 |
completed | April 15, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:01 a.m.