Triple
T26805790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Cavallucci Marini |
E671831
|
entity |
| Predicate | supporterCultureElement |
P198033
|
FINISHED |
| Object | nickname |
—
|
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: nickname | Statement: [I Cavallucci Marini, supporterCultureElement, nickname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supporterCultureElement Context triple: [I Cavallucci Marini, supporterCultureElement, nickname]
-
A.
supporterCulture
Indicates a relationship where an entity’s culture, norms, or practices are shaped by, aligned with, or strongly influenced by its supporters or fan base.
-
B.
supporterStyle
Indicates the characteristic manner or approach in which a supporter provides their support.
-
C.
supporterFeatures
Indicates that one entity provides supporting characteristics, capabilities, or functionalities that enhance or enable another entity.
-
D.
supporterElement
Indicates that one entity serves as a supporting element or component that provides structural, functional, or conceptual support to another entity.
-
E.
supporterOf
Indicates that one entity backs, advocates for, or provides assistance to another entity, cause, or organization.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
| PDg | Predicate description generation | batch_69fec4cee6a081908139ea6aa608f729 |
completed | May 9, 2026, 5:23 a.m. |
Created at: April 27, 2026, 4:26 a.m.