Triple

T4964094
Position Surface form Disambiguated ID Type / Status
Subject Pennsylvania and New Jersey E111477 entity
Predicate haveSharedHistoryIn P3438 FINISHED
Object colonial era of the Thirteen Colonies 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: colonial era of the Thirteen Colonies | Statement: [Pennsylvania and New Jersey, haveSharedHistoryIn, colonial era of the Thirteen Colonies]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: haveSharedHistoryIn
Context triple: [Pennsylvania and New Jersey, haveSharedHistoryIn, colonial era of the Thirteen Colonies]
  • A. sharesHistoryWith chosen
    Indicates that two entities have a common or overlapping past, such as shared experiences, events, or origins.
  • B. hasHistorySince
    Indicates that an entity has maintained a particular state, condition, or relationship continuously starting from a specified point in time.
  • C. hasHistoricalTieTo
    Indicates a relationship where one entity is historically connected or linked to another through past events, associations, or influences.
  • D. sharesCommonAncestorWith
    Indicates that two entities have at least one ancestor in common in their lineage or hierarchy.
  • E. haveSharedBorderSince
    Indicates that two entities have had a common boundary or border continuously from a specified point in time onward.
  • 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_69bd4419393c819086319a6fe4bf8542 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd72e49b048190bac55d9e7a6f7963 completed March 20, 2026, 4:16 p.m.
PD Predicate disambiguation batch_69bd71447fe88190bb62c5e8753da7a7 completed March 20, 2026, 4:09 p.m.
Created at: March 20, 2026, 1:32 p.m.