Triple
T22486539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spreadheads |
E555896
|
entity |
| Predicate | fanTerminologyOf |
P139921
|
FINISHED |
| Object | Widespread Panic fans |
—
|
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: Widespread Panic fans | Statement: [Spreadheads, fanTerminologyOf, Widespread Panic fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanTerminologyOf Context triple: [Spreadheads, fanTerminologyOf, Widespread Panic fans]
-
A.
fanTerm
Indicates that one entity is a term, label, or expression used by fans to refer to or describe another entity.
-
B.
fandomTerm
chosen
Indicates that one entity is a term, label, or piece of vocabulary specifically used within the fandom associated with another entity.
-
C.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
D.
fanOwned
Indicates that the entity is owned or controlled by fans, typically through collective or community-based ownership rather than traditional private or corporate ownership.
-
E.
fanBase
Indicates that one entity is the group of admirers or supporters devoted to another entity.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3da9588190abf2f96d3104edfb |
completed | April 29, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.