Triple

T22730255
Position Surface form Disambiguated ID Type / Status
Subject Battle of Paris (1814) E562113 entity
Predicate defensivePositions P89170 FINISHED
Object heights and fortifications around Paris, including Montmartre 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: heights and fortifications around Paris, including Montmartre | Statement: [Battle of Paris (1814), defensivePositions, heights and fortifications around Paris, including Montmartre]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: defensivePositions
Context triple: [Battle of Paris (1814), defensivePositions, heights and fortifications around Paris, including Montmartre]
  • A. defensivePositionHeldBy
    Indicates that a specific defensive position or role is occupied or maintained by a particular entity.
  • B. defensiveRole
    Indicates that an entity serves a protective or guarding function in relation to another entity or context.
  • C. hasDefensivePositions chosen
    Indicates that an entity possesses or controls locations, structures, or arrangements specifically organized for defense against potential threats or attacks.
  • D. primaryDefensiveLine
    Indicates the main line of defense that first engages or protects against an opposing force or threat.
  • E. nearDefensivePositionsOf
    Indicates that one entity is located in close proximity to the defensive positions or fortifications associated with another entity.
  • 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_69e24550859c81908727d91efc3a81b4 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1792cb9cc8190a7c45032427bca1a completed April 29, 2026, 3:21 a.m.
PD Predicate disambiguation batch_69eed2a971c0819088af574e40c9343f completed April 27, 2026, 3:06 a.m.
Created at: April 17, 2026, 3:21 p.m.