Triple

T1024098
Position Surface form Disambiguated ID Type / Status
Subject Operation Garden E22100 entity
Predicate codenameRelationship P10690 FINISHED
Object ground component of Operation Market Garden 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: ground component of Operation Market Garden | Statement: [Operation Garden, codenameRelationship, ground component of Operation Market Garden]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: codenameRelationship
Context triple: [Operation Garden, codenameRelationship, ground component of Operation Market Garden]
  • A. codenameUser
    Indicates that a user is assigned or associated with a particular codename.
  • B. isRelatedName
    Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
  • C. relationshipType chosen
    Indicates the specific kind of relationship that exists between two or more entities.
  • D. definesRelationshipBetween
    Indicates that one entity specifies or establishes the nature, type, or rules of a relationship that exists between two or more other entities.
  • E. relatedNameOfGod
    Indicates that one entity is a name, title, or designation that refers to or is associated with God.
  • 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_69a493d6e380819097b384986ffc315c completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b7e28df08190b5be7794442a6f21 completed March 1, 2026, 10:04 p.m.
PD Predicate disambiguation batch_69a4b72619cc8190932fdfa0c74dc055 completed March 1, 2026, 10:01 p.m.
Created at: March 1, 2026, 7:41 p.m.