Triple
T6576993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shungopavi |
E157191
|
entity |
| Predicate | isTraditionalSettlement |
P17528
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Shungopavi, isTraditionalSettlement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTraditionalSettlement Context triple: [Shungopavi, isTraditionalSettlement, true]
-
A.
traditionalSettlement
chosen
Indicates that an entity is a settlement characterized by long-established, customary, or historically rooted patterns of habitation and land use.
-
B.
isRuralSettlement
Indicates that a settlement is located in a rural area, typically characterized by low population density and limited urban infrastructure.
-
C.
traditionalSettlementArea
Indicates that an area is recognized as a traditional settlement zone associated with a particular group or community.
-
D.
isInlandSettlement
Indicates that a settlement is located away from the coast, without direct access to the sea or ocean.
-
E.
isLocatedInSettlement
Indicates that an entity is situated within or belongs to a specific human settlement, such as a town, village, or city.
- 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_69c6882b3a108190b3a9eb343ae4162c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acf93cb48190b54f5dd6febd34dc |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:54 p.m.