Triple
T28596011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Incubator:Help |
E723771
|
entity |
| Predicate | isPartOfHelpSystem |
P58477
|
FINISHED |
| Object | Wikimedia Incubator help namespace |
—
|
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 Incubator help namespace | Statement: [Incubator:Help, isPartOfHelpSystem, Wikimedia Incubator help namespace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfHelpSystem Context triple: [Incubator:Help, isPartOfHelpSystem, Wikimedia Incubator help namespace]
-
A.
isPartOfSystemWithFeature
Indicates that one entity belongs to a system that possesses a specified feature or characteristic.
-
B.
isPartOfAccessSystem
Indicates that something functions as a component or element within a larger access control or access management system.
-
C.
isInSystem
chosen
Indicates that one entity is located within, belongs to, or is contained by a particular system.
-
D.
isPartOfFramework
Indicates that one entity functions as a component, module, or element within a larger structured framework or system.
-
E.
partOfSystem
Indicates that one entity functions as a component or subsystem within the structure or organization of another entity.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 28, 2026, 4:21 a.m.