Triple
T28594440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esperanto Wikipedia |
E723735
|
entity |
| Predicate | hasInterlanguageLinks |
P82626
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Esperanto Wikipedia, hasInterlanguageLinks, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInterlanguageLinks Context triple: [Esperanto Wikipedia, hasInterlanguageLinks, yes]
-
A.
usesInterwikiLinks
chosen
Indicates that one entity includes or relies on interwiki links to reference or connect to content in other wikis.
-
B.
hasInternationalLink
Indicates that there exists a connection or association between entities that crosses national boundaries or involves multiple countries.
-
C.
hasRelatedLanguage
Indicates that one language is related to another through shared linguistic origins, features, or classification.
-
D.
hasNeighboringLanguages
Indicates that two languages are geographically or regionally adjacent to each other in their areas of use.
-
E.
hasWikipediaLanguageEdition
Indicates that a particular language has its own dedicated edition of Wikipedia available in that language.
- 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_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: April 28, 2026, 4:21 a.m.