Triple
T462300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Desventuradas Islands |
E7364
|
entity |
| Predicate | humanSettlementType |
P14278
|
FINISHED |
| Object | military outpost |
—
|
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: military outpost | Statement: [Desventuradas Islands, humanSettlementType, military outpost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humanSettlementType Context triple: [Desventuradas Islands, humanSettlementType, military outpost]
-
A.
hasPopulationCenterType
Indicates the classification of a population center by its type, such as city, town, village, or other settlement category.
-
B.
hasCityStatusSettlement
Indicates that a settlement possesses official recognition or designation as a city.
-
C.
urbanAreaType
Indicates the classification of an area based on its urban characteristics or development type (e.g., city, town, suburb, metropolitan region).
-
D.
hasMunicipalityType
Indicates that an administrative unit is classified as having a specific type or category of municipality (e.g., city, town, village).
-
E.
hadPrimarySettlementPattern
Indicates that an entity exhibited or was characterized by a particular dominant form or arrangement of human settlement.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efc09eac8190add4bb5823b53ba7 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2ede8eac081908dffade6a5e7950b |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef06d2fc8190b379d575215a8518 |
completed | Feb. 28, 2026, 1:35 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.