Triple
T8301706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian Wikinews |
E194362
|
entity |
| Predicate | editHistoryPublic |
P82613
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Norwegian Wikinews, editHistoryPublic, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editHistoryPublic Context triple: [Norwegian Wikinews, editHistoryPublic, yes]
-
A.
collectionHistory
Indicates the record of when, how, and from whom an item or set of items was acquired, transferred, or otherwise added to a collection over time.
-
B.
formatHistory
Indicates that one entity records or structures the sequence of past states, events, or changes associated with another entity into a specific format.
-
C.
operatorHistory
Indicates a record of past actions, states, or changes associated with a particular operator over time.
-
D.
classHistory
Indicates a relationship where an entity records or reflects the historical versions, changes, or evolution of a particular class over time.
-
E.
hasHistoryNote
Indicates that there is an associated historical note or record describing past events, changes, or context related to the subject.
- F. None of above. chosen
Provenance (4 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_69ca82e50ebc81909aa7b260c76bd757 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7e891030819097f4a26992a8b469 |
completed | March 31, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:53 p.m.