Triple
T28644307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basque Wikibooks |
E725010
|
entity |
| Predicate | hasMainNamespaceContent |
P198310
|
FINISHED |
| Object | textbook modules |
—
|
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: textbook modules | Statement: [Basque Wikibooks, hasMainNamespaceContent, textbook modules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainNamespaceContent Context triple: [Basque Wikibooks, hasMainNamespaceContent, textbook modules]
-
A.
hasNamespace
Indicates that one entity is associated with, defined within, or belongs to a particular namespace context provided by another entity.
-
B.
hasMainElements
Indicates that something possesses or is composed of its primary or most important constituent parts.
-
C.
hasMainSymbol
Indicates that one entity is designated as the primary or most representative symbol associated with another entity.
-
D.
hasNamespaces
Indicates that an entity is associated with one or more namespaces that define its scoping or organizational context.
-
E.
hasSubNamespace
Indicates that one namespace is a direct subordinate or contained namespace within another namespace.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fedd5a5f4c8190acce88db56303703 |
completed | May 9, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69fed910b31c8190ae837163d146738d |
completed | May 9, 2026, 6:49 a.m. |
| PDg | Predicate description generation | batch_69fedd5915588190bd884054e4be0414 |
completed | May 9, 2026, 7:08 a.m. |
Created at: April 28, 2026, 4:47 a.m.