Triple
T28595328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basque Wiktionary |
E723755
|
entity |
| Predicate | includesEntriesFor |
P18283
|
FINISHED |
| Object | Basque words |
—
|
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: Basque words | Statement: [Basque Wiktionary, includesEntriesFor, Basque words]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesEntriesFor Context triple: [Basque Wiktionary, includesEntriesFor, Basque words]
-
A.
eachDependencyEntryIncludes
Indicates that every individual dependency record or item contains or incorporates a specified element or set of information.
-
B.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
C.
includesElement
Indicates that one collection, set, or structure contains a specified element as a member or component.
-
D.
hasEntryOn
chosen
Indicates that one entity contains or includes an entry, record, or listing about another entity.
-
E.
selectionIncludes
Indicates that a chosen set or subset explicitly contains or covers the specified element(s) as part of the selection.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69ff1f3f94fc819095955299f50ab4ce |
completed | May 9, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69ff1ea47748819082f63d9b9d9c3e65 |
completed | May 9, 2026, 11:46 a.m. |
Created at: April 28, 2026, 4:21 a.m.