Triple
T25696230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alorese language |
E644326
|
entity |
| Predicate | isCoastalVarietyOf |
P159188
|
FINISHED |
| Object | Lamaholot-Alorese dialect continuum |
—
|
NE NERFINISHED |
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: Lamaholot-Alorese dialect continuum | Statement: [Alorese language, isCoastalVarietyOf, Lamaholot-Alorese dialect continuum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCoastalVarietyOf Context triple: [Alorese language, isCoastalVarietyOf, Lamaholot-Alorese dialect continuum]
-
A.
isCoastalTo
Indicates that one place is located along or directly borders the coastline of another body of water or coastal region.
-
B.
areCoastal
Indicates that the entities are located on or adjacent to a coastline or seashore.
-
C.
isCoastalOn
Indicates that one entity is located along or directly borders the coastline of another entity (such as a body of water or sea).
-
D.
isCoastalRegion
Indicates that a region is located along or directly adjacent to a sea or ocean coastline.
-
E.
isCoastalLocation
Indicates that a location is situated on or directly adjacent to a sea, ocean, or significant coastal body of water.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fbc4f1e88190bd5b195d92e44d3e |
completed | May 2, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 8:36 p.m.