Triple
T36312406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | /co/ |
E894097
|
entity |
| Predicate | hasUserbase |
P77700
|
FINISHED |
| Object | comic book fans |
—
|
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: comic book fans | Statement: [/co/, hasUserbase, comic book fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUserbase Context triple: [/co/, hasUserbase, comic book fans]
-
A.
hasUsers
Indicates that an entity is associated with one or more users who use, own, or are linked to it.
-
B.
hasGlobalFanBase
Indicates that an entity is widely recognized and followed by fans across multiple countries or regions.
-
C.
hasFanBaseFrom
Indicates that an entity has a significant group of supporters or followers originating from a specified place, group, or source.
-
D.
hasNotableConsumerBase
chosen
Indicates that an entity is recognized for having a significant or prominent group of consumers or users.
-
E.
hasUser
Indicates that an entity is associated with or linked to a specific user.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.