Triple

T2072631
Position Surface form Disambiguated ID Type / Status
Subject Pelusium E44848 entity
Predicate archaeologicalRemains P33764 FINISHED
Object fortifications 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: fortifications | Statement: [Pelusium, archaeologicalRemains, fortifications]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: archaeologicalRemains
Context triple: [Pelusium, archaeologicalRemains, fortifications]
  • A. archaeologicalFindsInclude
    Indicates that the set of archaeological finds at a site or context contains or encompasses the specified items or types of artifacts.
  • B. archaeologicalSiteIncludes chosen
    Indicates that an archaeological site contains, encompasses, or includes a specified feature, structure, artifact collection, or sub-area as part of its extent or composition.
  • C. notableArchaeologicalSite
    Indicates that a place is recognized as an archaeologically significant site, typically due to important historical remains, artifacts, or research findings.
  • D. hasArchaeologicalFeature
    Indicates that an entity possesses, contains, or is associated with a specific archaeological feature or structure.
  • E. cultSite
    Indicates a location that is or was used for religious or ritual worship activities.
  • 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_69a88916c2b48190a5ca2e9b12cad3ed completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abba0eaa5081908f6d6ff80f79b1c9 completed March 7, 2026, 5:39 a.m.
PD Predicate disambiguation batch_69abb7b0edac8190a58eabee55f73deb completed March 7, 2026, 5:29 a.m.
Created at: March 4, 2026, 7:41 p.m.