Triple
T8941442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cartier Island |
E212908
|
entity |
| Predicate | permanentCivilianSettlement |
P70045
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Cartier Island, permanentCivilianSettlement, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentCivilianSettlement Context triple: [Cartier Island, permanentCivilianSettlement, false]
-
A.
permanentHumanSettlement
chosen
Indicates that a location serves as a long-term, continuously inhabited place where humans live and establish enduring residence.
-
B.
mainSettlement
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
-
C.
humanSettlementType
Indicates the classification of a human settlement based on its form or function, such as village, town, or city.
-
D.
traditionalSettlement
Indicates that an entity is a settlement characterized by long-established, customary, or historically rooted patterns of habitation and land use.
-
E.
typicalSettlement
Indicates that the subject is a common or characteristic type of settlement typically found in the context of the object.
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66b9c14c8190b80c3df0cdba2747 |
completed | April 1, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:58 p.m.