Triple
T29754879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikimedia Foundation governance wiki |
E753001
|
entity |
| Predicate | hasEditorGroup |
P172400
|
FINISHED |
| Object | Wikimedia Foundation staff editors |
—
|
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: Wikimedia Foundation staff editors | Statement: [Wikimedia Foundation governance wiki, hasEditorGroup, Wikimedia Foundation staff editors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEditorGroup Context triple: [Wikimedia Foundation governance wiki, hasEditorGroup, Wikimedia Foundation staff editors]
-
A.
hasEditorType
Indicates that an entity has an associated kind or category of editor responsible for reviewing or modifying it.
-
B.
hasCollectionEditor
Indicates that an entity serves as the editor responsible for curating, managing, or overseeing a particular collection.
-
C.
hasFormerEditor
Indicates that an entity previously served as the editor of another entity but no longer holds that editorial role.
-
D.
hasEditingFeature
Indicates that an entity possesses a capability or function related to modifying or editing content.
-
E.
hasEditorScripting
Indicates that an entity provides or supports scripting capabilities specifically for editing or editor-related functionality.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 28, 2026, 7:56 p.m.