Triple

T15641230
Position Surface form Disambiguated ID Type / Status
Subject Mayaca E376068 entity
Predicate historicallyEntangledWith P16345 FINISHED
Object neighboring Florida indigenous groups 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: neighboring Florida indigenous groups | Statement: [Mayaca, historicallyEntangledWith, neighboring Florida indigenous groups]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallyEntangledWith
Context triple: [Mayaca, historicallyEntangledWith, neighboring Florida indigenous groups]
  • A. historicallyLinked chosen
    Indicates that two entities are connected through a shared or related historical event, period, or development.
  • B. historicallyAttracted
    Indicates that one entity has experienced attraction toward another at some point in the past.
  • C. hasHistoricalInfluenceFrom
    Indicates that one entity’s characteristics, development, or significance have been shaped or affected by the past actions, ideas, or legacy of another entity.
  • D. historicallyGroupedWith
    Indicates that two or more entities have been associated or classified together in the past based on historical context, usage, or tradition, even if they are no longer grouped that way.
  • E. eraOfHistoricalAssociation
    Indicates the historical time period during which the association or relationship between the entities took place.
  • 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_69d85cd035a48190b73d5579ab73969a completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04ed23d688190bea996f90989d406 completed April 16, 2026, 2:52 a.m.
PD Predicate disambiguation batch_69deda890140819082608931e993dd61 completed April 15, 2026, 12:23 a.m.
Created at: April 10, 2026, 4:15 a.m.