Triple
T13073320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Samareño |
E329506
|
entity |
| Predicate | isCoastalPopulation |
P108301
|
FINISHED |
| Object | many residents live in coastal areas |
—
|
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: many residents live in coastal areas | Statement: [Northern Samareño, isCoastalPopulation, many residents live in coastal areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCoastalPopulation Context triple: [Northern Samareño, isCoastalPopulation, many residents live in coastal areas]
-
A.
isCoastalCityCodeFor
Indicates that a given code uniquely identifies a city that is located on or near a coast.
-
B.
isCoastalCommunity
Indicates that a community is located along a coast or shoreline and is directly associated with a nearby sea or ocean.
-
C.
isCoastalArea
Indicates that a given area is located along or directly adjacent to a sea or ocean coastline.
-
D.
isCoastalOn
Indicates that one entity is located along or directly borders the coastline of another entity (such as a body of water or sea).
-
E.
isCoastalRegion
Indicates that a region is located along or directly adjacent to a sea or ocean coastline.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d981160e388190bab942a2ded2903e |
completed | April 10, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d980e622e8819087a69bfb1660dd64 |
completed | April 10, 2026, 10:59 p.m. |
Created at: April 9, 2026, 9 p.m.