Triple

T2944151
Position Surface form Disambiguated ID Type / Status
Subject Huastec E79459 entity
Predicate historicalSeparationFromOtherMayan P13031 FINISHED
Object early split 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: early split | Statement: [Huastec, historicalSeparationFromOtherMayan, early split]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalSeparationFromOtherMayan
Context triple: [Huastec, historicalSeparationFromOtherMayan, early split]
  • A. hasPreColumbianCollectionRegions
    Indicates that an entity possesses collections originating from specific geographic regions dating to the pre-Columbian period.
  • B. historicalIsolationFrom chosen
    Indicates that one entity has been historically separated or cut off from another entity, typically due to geographic, political, cultural, or social barriers over an extended period.
  • C. historicallyDividedInto
    Indicates that an entity was separated into multiple distinct parts or regions during a past historical period.
  • D. wasDividedFromYear
    Indicates that an entity began to be separated or partitioned starting from a specified year.
  • E. separatedFromCubaBy
    Indicates that one entity is divided or kept apart from Cuba by a specified physical or conceptual boundary.
  • 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_69ad8b1089588190b74d9e2505e45762 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad98b0db5081908e84def20a5e4a2d completed March 8, 2026, 3:41 p.m.
PD Predicate disambiguation batch_69ad96088fb481909976b436c2b729d9 completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 2:56 p.m.