Triple
T103951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceylon (Dutch Ceylon) |
E2099
|
entity |
| Predicate | regionIncluded |
P285
|
FINISHED |
| Object | coastal areas of Sri Lanka |
—
|
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: coastal areas of Sri Lanka | Statement: [Ceylon (Dutch Ceylon), regionIncluded, coastal areas of Sri Lanka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionIncluded Context triple: [Ceylon (Dutch Ceylon), regionIncluded, coastal areas of Sri Lanka]
-
A.
hasRegion
chosen
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
B.
excludesRegion
Indicates that one entity explicitly omits, leaves out, or does not apply to a specified region or geographic area.
-
C.
usedInRegion
Indicates that something is utilized or applied within a specific geographic or administrative region.
-
D.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
E.
regionType
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a25711f6788190a22252ea3a3af394 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563be81c81908ccc5ed44edd6b8e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.