Triple
T8380150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CentralNotice |
E197667
|
entity |
| Predicate | usedBy |
P260
|
FINISHED |
| Object | Wikidata |
E37902
|
NE 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: Wikidata | Statement: [CentralNotice, usedBy, Wikidata]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wikidata Context triple: [CentralNotice, usedBy, Wikidata]
-
A.
Wikidata
chosen
Wikidata is a collaboratively edited, multilingual knowledge base that provides structured data to support Wikipedia and other Wikimedia projects.
-
B.
Wikidata Query Service
Wikidata Query Service is an online SPARQL endpoint and interface that allows users to query and explore structured data stored in Wikidata.
-
C.
Wikibase
Wikibase is a free, open-source software suite developed by Wikimedia for storing, managing, and querying structured, linked data.
-
D.
Wikidata development team
The Wikidata development team is the group of software engineers and product specialists responsible for building and maintaining the Wikidata project under Wikimedia Deutschland.
-
E.
Semantic MediaWiki
Semantic MediaWiki is an extension to the MediaWiki platform that adds semantic annotation and querying capabilities, turning wiki content into a structured, queryable knowledge base.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80c57080819097eef2b7e46eaaee |
completed | March 31, 2026, 8:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cecc2b3890819091f8947ebf31bad0 |
completed | April 2, 2026, 8:06 p.m. |
Created at: March 30, 2026, 6:02 p.m.