Triple
T28594490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esperanto Wiktionary |
E723736
|
entity |
| Predicate | hasProjectScope |
P397
|
FINISHED |
| Object | words in Esperanto |
—
|
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: words in Esperanto | Statement: [Esperanto Wiktionary, hasProjectScope, words in Esperanto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProjectScope Context triple: [Esperanto Wiktionary, hasProjectScope, words in Esperanto]
-
A.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
-
B.
hasScope
chosen
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
-
C.
hasProject
Indicates that an entity is associated with or responsible for a particular project.
-
D.
isOnProjectBy
Indicates that an entity is assigned to or working on a project under the responsibility or authorship of another entity.
-
E.
isOnProject
Indicates that an entity is currently assigned to, involved with, or working on a particular project.
- 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_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
Created at: April 28, 2026, 4:21 a.m.