Triple

T639793
Position Surface form Disambiguated ID Type / Status
Subject Battle of the Bulge Memorial E16708 entity
Predicate locatedInSection P40 FINISHED
Object Section 21 of Arlington National Cemetery 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: Section 21 of Arlington National Cemetery | Statement: [Battle of the Bulge Memorial, locatedInSection, Section 21 of Arlington National Cemetery]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInSection
Context triple: [Battle of the Bulge Memorial, locatedInSection, Section 21 of Arlington National Cemetery]
  • A. navigableInSection
    Indicates that something can be successfully moved through, accessed, or traversed within a specified section or segment.
  • B. locatedAfter
    Indicates that one entity is positioned later than another along a defined sequence, order, or spatial/temporal axis.
  • C. locatedIn chosen
    Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
  • D. locatedBetween
    Indicates that one entity is positioned spatially between two other reference entities.
  • E. locatedOff
    Indicates that one entity is situated away from, but in the vicinity of, another entity or reference point, rather than directly on or within it.
  • 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_69a4936be1c88190af56540324b57da7 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49f00260081909d1a679182e23d10 completed March 1, 2026, 8:18 p.m.
PD Predicate disambiguation batch_69a49d0830008190a26ee158ed4dd1fe completed March 1, 2026, 8:09 p.m.
Created at: March 1, 2026, 7:35 p.m.