Triple
T3292770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monito Island |
E69139
|
entity |
| Predicate | permanentSettlements |
P45139
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Monito Island, permanentSettlements, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentSettlements Context triple: [Monito Island, permanentSettlements, none]
-
A.
humanSettlementType
Indicates the classification of a human settlement based on its form or function, such as village, town, or city.
-
B.
mainSettlement
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
-
C.
hasHumanSettlement
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
-
D.
notableSettlementCountry
Indicates that a country is notably associated with a particular settlement, such as being its primary or most recognized national affiliation.
-
E.
humanSettlementStatus
chosen
Indicates the classification of a place in terms of its status as a human settlement (e.g., whether and how it is recognized or designated as a populated place).
- 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_69ad859d45748190b0742408c954b39f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb07379dc8190b7bb409bcf42bdd6 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada42407dc81909f60d7a14e1b7934 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.