Triple
T32029259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yámana |
E817903
|
entity |
| Predicate | mainSettlementToday |
P13187
|
FINISHED |
| Object | Puerto Williams |
—
|
NE NERFINISHED |
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: Puerto Williams | Statement: [Yámana, mainSettlementToday, Puerto Williams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSettlementToday Context triple: [Yámana, mainSettlementToday, Puerto Williams]
-
A.
mainSettlement
chosen
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
-
B.
administrativeDivisionToday
Indicates that one entity currently functions as an administrative subdivision or jurisdictional unit within the other.
-
C.
mainSettlementLocatedOn
Indicates that the primary settlement of an area is situated on or directly adjacent to a specified geographic feature or location.
-
D.
currentSettlement
Indicates that an entity is presently located in or associated with a particular settlement (such as a town, city, or village).
-
E.
mainSettlementsCharacter
Indicates that a settlement serves as a primary or defining location that characterizes a larger area, region, or context.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 12:18 a.m.