Triple
T8302470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikimedia Incubator |
E194379
|
entity |
| Predicate | hasProjectInformationPage |
P82625
|
FINISHED |
| Object | Incubator:Main Page |
—
|
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: Incubator:Main Page | Statement: [Wikimedia Incubator, hasProjectInformationPage, Incubator:Main Page]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProjectInformationPage Context triple: [Wikimedia Incubator, hasProjectInformationPage, Incubator:Main Page]
-
A.
hasProject
Indicates that an entity is associated with or responsible for a particular project.
-
B.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
-
C.
hasProjectType
Indicates that an entity is associated with, or classified under, a specific type or category of project.
-
D.
hasSubproject
Indicates that a project includes another project as a subordinate or component part within its overall structure.
-
E.
hasInformationService
Indicates that one entity provides, operates, or is associated with an information-related service for another entity.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7e8a45348190a7895b33abcb64c9 |
completed | March 31, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
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.