Triple
T18270217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turning Point |
E437587
|
entity |
| Predicate | hasFandomRecognition |
P87366
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Turning Point, hasFandomRecognition, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFandomRecognition Context triple: [Turning Point, hasFandomRecognition, true]
-
A.
hasFandomDesignation
Indicates that an entity has a specific name or label used by its fan community to refer to it or its fandom.
-
B.
hasFanCommunity
Indicates that an entity is associated with a group of fans who actively follow, support, or engage around it.
-
C.
fandomSignificance
chosen
Indicates the degree to which something holds importance, influence, or prominence within a particular fan community or fandom context.
-
D.
fandomReception
Indicates how a work, character, or creator is perceived, evaluated, and responded to by its fan community.
-
E.
fandomScope
Indicates the extent or boundaries of a fandom-related relationship, such as how broadly or narrowly a fan’s interest, participation, or recognition applies.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff7d4f88819084123ed6c9e7e5b8 |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.