Triple
T18597765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ekstrabladet.dk |
E454535
|
entity |
| Predicate | hasOnlinePresenceSince |
P18972
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [ekstrabladet.dk, hasOnlinePresenceSince, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnlinePresenceSince Context triple: [ekstrabladet.dk, hasOnlinePresenceSince, 1990s]
-
A.
hasOnlineActivity
Indicates that an entity engages in or possesses some form of activity or presence on the internet or digital platforms.
-
B.
primaryNetworkSince
Indicates that an entity has been designated as the main or preferred network connection starting from a specific point in time.
-
C.
partOfNetworkSince
Indicates that an entity has been a member or component of a particular network starting from a specified point in time.
-
D.
onlinePresence
chosen
Indicates that an entity maintains a presence or representation on the internet, such as through websites, profiles, or digital platforms.
-
E.
existsSince
Indicates that an entity has been in existence or valid from a specified point in time onward.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5474d934481909b4afd5ef9031c73 |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.