Triple
T26847452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mocoví |
E675962
|
entity |
| Predicate | modernSettlementPattern |
P1830
|
FINISHED |
| Object | rural 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: rural communities | Statement: [Mocoví, modernSettlementPattern, rural communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernSettlementPattern Context triple: [Mocoví, modernSettlementPattern, rural communities]
-
A.
modernSettlement
Indicates that the subject is a contemporary or currently existing human settlement located at the object.
-
B.
modernSettlementArea
Indicates the geographic area occupied by a settlement in its modern or current form.
-
C.
hadPrimarySettlementPattern
chosen
Indicates that an entity exhibited or was characterized by a particular dominant form or arrangement of human settlement.
-
D.
modernSettlementCoreOf
Indicates that a modern settlement functions as the central or primary core area of another, broader settlement entity.
-
E.
traditionalSettlement
Indicates that an entity is a settlement characterized by long-established, customary, or historically rooted patterns of habitation and land use.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 5:13 a.m.