Triple
T33815733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duncan |
E866667
|
entity |
| Predicate | hasFandomFor |
P191982
|
FINISHED |
| Object | Tucker Crowe |
—
|
NE NERFINISHED |
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: Tucker Crowe | Statement: [Duncan, hasFandomFor, Tucker Crowe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFandomFor Context triple: [Duncan, hasFandomFor, Tucker Crowe]
-
A.
hasFandomAssociation
chosen
Indicates a relationship where an entity is associated with, connected to, or recognized within a particular fandom or fan community.
-
B.
hasFandomElement
Indicates that something includes, features, or is associated with an element derived from or related to a fandom.
-
C.
hasFandomDesignation
Indicates that an entity has a specific name or label used by its fan community to refer to it or its fandom.
-
D.
fandomType
Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
-
E.
fandomSharedWith
Indicates that two or more entities share interest or participation in the same fandom.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: May 1, 2026, 1:46 a.m.