Triple
T19984418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Trio |
E493898
|
entity |
| Predicate | hasFandomTermType |
P115447
|
FINISHED |
| Object | ship-neutral grouping name |
—
|
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: ship-neutral grouping name | Statement: [Golden Trio, hasFandomTermType, ship-neutral grouping name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFandomTermType Context triple: [Golden Trio, hasFandomTermType, ship-neutral grouping name]
-
A.
hasFandomDesignation
chosen
Indicates that an entity has a specific name or label used by its fan community to refer to it or its fandom.
-
B.
hasFictionalType
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
-
C.
fandomType
Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
-
D.
hasMythType
Indicates that an entity is associated with or classified under a particular type or category of myth.
-
E.
hasTerm
Indicates that an entity includes, is associated with, or is defined by a specific term or condition.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d157d088190af861608936e59b7 |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:29 p.m.