Triple
T12739756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Göz-Göz |
E304457
|
entity |
| Predicate | hasFanCultureRole |
P14308
|
FINISHED |
| Object | rallying chant |
—
|
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: rallying chant | Statement: [Göz-Göz, hasFanCultureRole, rallying chant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFanCultureRole Context triple: [Göz-Göz, hasFanCultureRole, rallying chant]
-
A.
hasFictionalRole
Indicates that an entity plays or is assigned a specific role within a fictional work or narrative.
-
B.
hasFanCommunity
Indicates that an entity is associated with a group of fans who actively follow, support, or engage around it.
-
C.
hasInUniverseRole
Indicates that an entity holds or performs a specific role or function within a particular fictional or defined universe.
-
D.
fanCultureElement
chosen
Indicates a relationship where something is a notable practice, artifact, or tradition that characterizes or expresses a particular fan culture.
-
E.
subjectOfFandom
Indicates that one entity is the focus or object of another entity’s fandom, admiration, or devoted interest.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:26 p.m.