Triple
T22486538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spreadheads |
E555896
|
entity |
| Predicate | identifiesWith |
P310
|
FINISHED |
| Object | Widespread Panic fan identity |
—
|
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 fan identity | Statement: [Spreadheads, identifiesWith, Widespread Panic fan identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiesWith Context triple: [Spreadheads, identifiesWith, Widespread Panic fan identity]
-
A.
correspondsWith
Indicates that two entities are in mutual alignment or agreement, such that one matches, parallels, or is equivalent to the other in a specified respect.
-
B.
coincidesWith
Indicates that two entities occupy the same position, time, or state such that they exactly overlap or occur together.
-
C.
identifiedUsing
Indicates that one entity was recognized, distinguished, or determined by means of a specified method, tool, or identifier.
-
D.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
E.
recognizedAs
chosen
Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of 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.