Triple

T3936579
Position Surface form Disambiguated ID Type / Status
Subject Amman Citadel E90925 entity
Predicate containsStructureFrom P52639 FINISHED
Object Roman architecture 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: Roman architecture | Statement: [Amman Citadel, containsStructureFrom, Roman architecture]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: containsStructureFrom
Context triple: [Amman Citadel, containsStructureFrom, Roman architecture]
  • A. hasStructureAbove
    Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
  • B. containsAsSubstructure
    Indicates that one structure includes another structure entirely within it as a component or embedded part.
  • 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. hasStructureType
    Indicates that an entity possesses or is classified by a specific structural type or configuration.
  • E. supportsStructure
    Indicates that one entity bears or provides physical support to another entity, helping to hold it up or maintain its structural stability.
  • 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_69aed95f26e0819094b0e71974543a19 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeedceab608190934293d432f14476 completed March 9, 2026, 3:57 p.m.
PD Predicate disambiguation batch_69aee7625ad4819097e4e8a168c19274 completed March 9, 2026, 3:29 p.m.
PDg Predicate description generation batch_69aeed3260cc8190bf294bdab507b1f9 completed March 9, 2026, 3:54 p.m.
Created at: March 9, 2026, 3:23 p.m.