Triple
T28594977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgarian Wikivoyage |
E723747
|
entity |
| Predicate | editingInterface |
P165468
|
FINISHED |
| Object | MediaWiki |
—
|
NE NERFINISHED |
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: MediaWiki | Statement: [Bulgarian Wikivoyage, editingInterface, MediaWiki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editingInterface Context triple: [Bulgarian Wikivoyage, editingInterface, MediaWiki]
-
A.
editingIs
Indicates that one entity is performing or undergoing the process of editing another entity.
-
B.
editingMode
Indicates that an entity is currently in, or associated with, a state where its content or properties can be modified or edited.
-
C.
editingBody
Indicates that one entity is serving as the editorial body responsible for reviewing, modifying, or overseeing the content or work of another entity.
-
D.
editorStart
Indicates the point in time or position at which an editor begins working on, modifying, or reviewing a content item or resource.
-
E.
editorCommunity
Indicates a relationship where an editor is associated with, participates in, or belongs to a particular community.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 28, 2026, 4:21 a.m.