Triple
T6145187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kawésqar |
E137056
|
entity |
| Predicate | modernResidencePattern |
P6740
|
FINISHED |
| Object | settled communities |
—
|
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: settled communities | Statement: [Kawésqar, modernResidencePattern, settled communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernResidencePattern Context triple: [Kawésqar, modernResidencePattern, settled communities]
-
A.
residencyPattern
chosen
Indicates the typical way an entity resides or occupies a place over time, such as its usual location, duration, or frequency of stay.
-
B.
housingPattern
Indicates the typical arrangement or distribution of housing units or residential structures within a given area or context.
-
C.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
D.
residence
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other entity.
-
E.
modernLocality
Indicates that an entity is located in, associated with, or corresponds to a present-day geographic or administrative locality.
- 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_69c008a2c6308190a56519b22d55d083 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cdd2dc0819080a4adf0cead3603 |
completed | March 22, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:16 p.m.