Triple

T25609148
Position Surface form Disambiguated ID Type / Status
Subject Phoenix Shot Tower E641995 entity
Predicate significantMaterial P163021 FINISHED
Object load-bearing brick walls 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: load-bearing brick walls | Statement: [Phoenix Shot Tower, significantMaterial, load-bearing brick walls]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: significantMaterial
Context triple: [Phoenix Shot Tower, significantMaterial, load-bearing brick walls]
  • A. materialSignificance
    Indicates that one entity has substantial importance, influence, or impact on another in a concrete or consequential way.
  • B. hasMaterialSignificance
    Indicates that something holds notable importance, relevance, or consequence in a given context or situation.
  • C. materiality
    Indicates that something has the quality of being material or physically substantial, as opposed to abstract or immaterial.
  • D. significantResource
    Indicates that one entity serves as an important or substantial resource (e.g., material, financial, informational, or human) for another entity.
  • E. significantPort
    Indicates that a port holds major importance in terms of trade, transportation, or strategic relevance within a given context.
  • 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_69e75dc6ccf081908d49578fd36a76d5 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f63639a84c81909d700a539b458b42 completed May 2, 2026, 5:36 p.m.
PD Predicate disambiguation batch_69f63182f1408190bddc1214fcbd6145 completed May 2, 2026, 5:16 p.m.
PDg Predicate description generation batch_69f6352df6148190bc10772cd40bd7b3 completed May 2, 2026, 5:32 p.m.
Created at: April 21, 2026, 4:40 p.m.