Triple

T7432665
Position Surface form Disambiguated ID Type / Status
Subject Eboracum E171528 entity
Predicate hadStructure P76368 FINISHED
Object legionary fortress 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: legionary fortress | Statement: [Eboracum, hadStructure, legionary fortress]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadStructure
Context triple: [Eboracum, hadStructure, legionary fortress]
  • A. hasHumanStructure
    Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
  • B. mayHaveStructure
    Indicates that an entity is allowed or able to possess a particular internal organization, configuration, or structural form, though not necessarily required to do so.
  • C. usedStructure
    Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
  • D. affectedStructure
    Indicates that one entity is the structure, component, or part that is impacted, altered, or influenced by another entity or event.
  • E. builtStructureFor
    Indicates that one entity constructed or assembled a structure specifically intended for the use, benefit, or purpose of another entity.
  • F. None of above. chosen

Provenance (4 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_69c68a63491881909281f73d4d5643bf completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f325ea908190b668fd4ce646f1e6 completed March 27, 2026, 9:14 p.m.
PD Predicate disambiguation batch_69c6f038582c8190bac77c9b5a34b862 completed March 27, 2026, 9:01 p.m.
PDg Predicate description generation batch_69c6f0be2b1c8190bea06100a7caef2b completed March 27, 2026, 9:03 p.m.
Created at: March 27, 2026, 3:12 p.m.