Triple
T16696705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opium |
E405733
|
entity |
| Predicate | fanbaseAlsoKnownAs |
P65078
|
FINISHED |
| Object | Opium community |
—
|
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: Opium community | Statement: [Opium, fanbaseAlsoKnownAs, Opium community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanbaseAlsoKnownAs Context triple: [Opium, fanbaseAlsoKnownAs, Opium community]
-
A.
fanBaseName
chosen
Indicates the name by which the collective group of fans of a particular person, group, or entity is known.
-
B.
hasFanBaseFrom
Indicates that an entity has a significant group of supporters or followers originating from a specified place, group, or source.
-
C.
fanBase
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
D.
fanBaseRelationship
Indicates a relationship in which one party is a fan or supporter of another, typically involving admiration, following, or dedicated interest.
-
E.
hasFanBaseDepictedAs
Indicates that an entity has a fan base that is visually or narratively represented in some form (e.g., in media, artwork, or documentation).
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37eadc35881909fb0cc405a0e2fae |
completed | April 18, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.