Triple

T34446819
Position Surface form Disambiguated ID Type / Status
Subject Red Line Agreement E884251 entity
Predicate definesBoundaryAs P15022 FINISHED
Object red line on map of former Ottoman Empire 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: red line on map of former Ottoman Empire | Statement: [Red Line Agreement, definesBoundaryAs, red line on map of former Ottoman Empire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: definesBoundaryAs
Context triple: [Red Line Agreement, definesBoundaryAs, red line on map of former Ottoman Empire]
  • A. setsBoundary chosen
    Indicates that one entity defines or forms the limiting edge or border of another entity.
  • B. formsBoundaryType
    Indicates that one entity serves as a specific type of boundary for another entity.
  • C. proposesBoundary
    Indicates that one entity suggests or puts forward a specific boundary or limit to be considered or adopted in relation to another entity or context.
  • D. isBoundaryFor
    Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
  • E. boundaryCondition
    Indicates the specific constraints or values imposed at the limits or edges of a system, domain, or process that govern its behavior there.
  • 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_69f349c607688190b553539d14901a35 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69fe8f74748c8190bd14a856c057f9f7 completed May 9, 2026, 1:35 a.m.
PD Predicate disambiguation batch_69fe8e7ed8088190929e0df67aca4de9 completed May 9, 2026, 1:31 a.m.
Created at: May 1, 2026, 2 a.m.