Triple
T17198296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fernández Vial |
E417410
|
entity |
| Predicate | hasLocalSupport |
P126699
|
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: [Fernández Vial, hasLocalSupport, passionate fan base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalSupport Context triple: [Fernández Vial, hasLocalSupport, passionate fan base]
-
A.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
B.
supportsLocation
Indicates that one entity provides the necessary structure, foundation, or capacity to hold, host, or accommodate another entity at a particular place or position.
-
C.
hasAgencySupport
Indicates that an entity receives backing, assistance, or sponsorship from an agency.
-
D.
hasLocalImpact
Indicates that an entity produces effects or consequences within a specific local area or community.
-
E.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42daca29081909837494d8d516634 |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e39c2fedb881908bfed2c3e5f2616a |
completed | April 18, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:38 a.m.