Triple
T14710341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twilight fandom |
E345530
|
entity |
| Predicate | hasStrongOnlinePresence |
P34365
|
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: [Twilight fandom, hasStrongOnlinePresence, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrongOnlinePresence Context triple: [Twilight fandom, hasStrongOnlinePresence, true]
-
A.
hasOnlinePlatform
Indicates that an entity operates, maintains, or is associated with a presence or service on an online platform.
-
B.
notableOnlinePresence
chosen
Indicates that an entity maintains a significant, recognizable, or influential presence in online platforms or digital media.
-
C.
hasOnlineActivity
Indicates that an entity engages in or possesses some form of activity or presence on the internet or digital platforms.
-
D.
hasOnlineCommunity
Indicates that an entity maintains or is associated with a community that interacts primarily through online platforms or digital channels.
-
E.
hasSocialEngagement
Indicates that an entity participates in or maintains some form of social interaction, activity, or relationship with others.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb9814e0c8190984ac30d276499cc |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.