Triple

T530419
Position Surface form Disambiguated ID Type / Status
Subject Iron Age E12209 entity
Predicate typicalSociety P12230 FINISHED
Object chiefdoms 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: chiefdoms | Statement: [Iron Age, typicalSociety, chiefdoms]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalSociety
Context triple: [Iron Age, typicalSociety, chiefdoms]
  • A. typicalIn chosen
    Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
  • B. typicalAudience
    Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
  • C. typicalPractice
    Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
  • D. socialIssue
    Indicates a relationship where something is recognized or treated as a problem or concern affecting society or a community at large.
  • E. communalAspect
    Indicates that something involves or emphasizes shared participation, ownership, or experience within a group or community.
  • 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_69a4933208e88190891f5debab1b776d completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4985e51908190a34aa82ea9dbee1e completed March 1, 2026, 7:49 p.m.
PD Predicate disambiguation batch_69a494b257108190a537dffbb9d621b5 completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:32 p.m.