Triple
T28627792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Wikipedia |
E724567
|
entity |
| Predicate | namespaceSystem |
P23103
|
FINISHED |
| Object | MediaWiki namespaces |
—
|
NE NERFINISHED |
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: MediaWiki namespaces | Statement: [Italian Wikipedia, namespaceSystem, MediaWiki namespaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namespaceSystem Context triple: [Italian Wikipedia, namespaceSystem, MediaWiki namespaces]
-
A.
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.
-
B.
packageSystem
Indicates a relationship where an item or component is organized, bundled, or managed within a particular packaging or distribution system.
-
C.
usesNamingSystem
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
-
D.
systemName
Indicates that an entity has a specific system-level name or identifier assigned to it.
-
E.
moduleSystem
Indicates a relationship where one entity functions as or uses a particular module system to organize, load, or manage modular components.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 4:36 a.m.