Triple

T36076511
Position Surface form Disambiguated ID Type / Status
Subject Amana (settlement movement) E1043508 entity
Predicate roleInSettlements P89920 FINISHED
Object planning of settlements 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: planning of settlements | Statement: [Amana (settlement movement), roleInSettlements, planning of settlements]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInSettlements
Context triple: [Amana (settlement movement), roleInSettlements, planning of settlements]
  • A. nearbySettlementRole
    Indicates that one settlement has a specific functional or contextual role in relation to a nearby settlement.
  • B. organizedSettlement chosen
    Indicates that an entity actively planned, coordinated, and arranged the establishment or occurrence of a settlement.
  • C. mainSettlement
    Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
  • D. hasHumanSettlement
    Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
  • 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_69f76e3154908190a6f702671c2bea08 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_6a0174142430819084aa1235500b9d3b completed May 11, 2026, 6:15 a.m.
PD Predicate disambiguation batch_6a0171a6e0088190958679bb6cb24a70 completed May 11, 2026, 6:05 a.m.
Created at: May 3, 2026, 4:08 p.m.