Triple
T4698080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lilywhites |
E104197
|
entity |
| Predicate | associatedWithFanCulture |
P14308
|
FINISHED |
| Object | chants |
—
|
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: chants | Statement: [The Lilywhites, associatedWithFanCulture, chants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFanCulture Context triple: [The Lilywhites, associatedWithFanCulture, chants]
-
A.
hasFanCommunity
Indicates that an entity is associated with a group of fans who actively follow, support, or engage around it.
-
B.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
C.
fandomCulture
Indicates a relationship where one entity is associated with, shaped by, or participates in the shared practices, norms, and creative activities of a particular fan community.
-
D.
fanCultureElement
chosen
Indicates a relationship where something is a notable practice, artifact, or tradition that characterizes or expresses a particular fan culture.
-
E.
fanTerm
Indicates that one entity is a term, label, or expression used by fans to refer to or describe 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.