Triple
T1142914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Java Island (Java-eiland) |
E23494
|
entity |
| Predicate | hasLanguageOfToponym |
P24399
|
FINISHED |
| Object | Dutch |
—
|
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: Dutch | Statement: [Java Island (Java-eiland), hasLanguageOfToponym, Dutch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfToponym Context triple: [Java Island (Java-eiland), hasLanguageOfToponym, Dutch]
-
A.
hasToponymicForm
Indicates that one entity is a toponymic (place-name-based) form or variant derived from another entity.
-
B.
hasDemonym
Indicates that one entity is the term (demonym) used to refer to the inhabitants or natives of another entity (typically a place).
-
C.
isLinguaFrancaOf
Indicates that a language serves as a common medium of communication between speakers of different native languages within a particular region, community, or context.
-
D.
hasEndonym
Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
-
E.
hasToponymicUse
Indicates that a term or name is used as a toponym, i.e., as a place name or geographic designation.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc4e93d48190b9fea886bf61aad7 |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4d4104819084027a043c6118cb |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bbb9fb4c81909dd39c496893c21b |
completed | March 1, 2026, 10:20 p.m. |
Created at: March 1, 2026, 7:44 p.m.