Triple
T1735063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikidata |
E37902
|
entity |
| Predicate | WikibaseItemNamespace |
P23103
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [Wikidata, WikibaseItemNamespace, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WikibaseItemNamespace Context triple: [Wikidata, WikibaseItemNamespace, 0]
-
A.
namedSpace
Indicates that an entity has been assigned or is associated with a specific name within a particular namespace or naming context.
-
B.
hasWikidataProperty
Indicates that one entity is associated with a specific Wikidata property used to describe or qualify it.
-
C.
namespaceURI
Indicates the URI that defines the namespace to which a given identifier, element, or resource belongs.
-
D.
namespace
chosen
Indicates a scoping relationship in which identifiers or symbols are grouped under a specific context or name to avoid conflicts and organize them.
-
E.
nestName
Indicates that an entity has or is associated with a specific nest’s name.
- 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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab5c553e508190b0f511b05e07fa20 |
completed | March 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69aa61c25a648190892de94c997fb983 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.