Triple
T11893495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dérbi Paulista |
E282976
|
entity |
| Predicate | hasFanBaseFeature |
P95750
|
FINISHED |
| Object | large fan bases on both sides |
—
|
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: large fan bases on both sides | Statement: [Dérbi Paulista, hasFanBaseFeature, large fan bases on both sides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFanBaseFeature Context triple: [Dérbi Paulista, hasFanBaseFeature, large fan bases on both sides]
-
A.
hasFanBaseFrom
Indicates that an entity has a significant group of supporters or followers originating from a specified place, group, or source.
-
B.
hasFan
Indicates that an entity is the admirer, supporter, or enthusiast of another entity.
-
C.
hasFanBaseTension
Indicates a relationship where there is conflict, rivalry, or strained relations between the fan bases of the related entities.
-
D.
hasFanBaseType
chosen
Indicates that an entity has a particular type or category of fan base associated with it.
-
E.
hasFanCommunity
Indicates that an entity is associated with a group of fans who actively follow, support, or engage around it.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8dd1172988190a2c13d37220f2f93 |
completed | April 10, 2026, 11:20 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.