Triple

T13506271
Position Surface form Disambiguated ID Type / Status
Subject Genevois historical region E321021 entity
Predicate hasSharedPoliticalHistory P7843 FINISHED
Object true 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: true | Statement: [Genevois historical region, hasSharedPoliticalHistory, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSharedPoliticalHistory
Context triple: [Genevois historical region, hasSharedPoliticalHistory, true]
  • A. hasSharedBorderHistoryWith
    Indicates that two entities have a history of sharing a common border or boundary at some point in time.
  • B. hasSharedColonialHistory
    Indicates that the related entities were subject to, or part of, the same colonial power or colonial system during a historical period.
  • C. hasPoliticalAlly
    Indicates that one entity supports and cooperates with another in a political context, treating them as an ally in political activities or objectives.
  • D. hasHistoricalPolity
    Indicates a relationship where an entity is associated with a political unit or state that existed in the past.
  • E. hasHistoricalTieTo chosen
    Indicates a relationship where one entity is historically connected or linked to another through past events, associations, or influences.
  • 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_69d807629d6c8190998f1b9bb12d2ed0 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaf8259a08190ada13c4a3078f07d completed April 12, 2026, 2:43 p.m.
PD Predicate disambiguation batch_69dbae0b63748190b5e207f84b2532ea completed April 12, 2026, 2:36 p.m.
Created at: April 9, 2026, 9:43 p.m.