Triple

T4430520
Position Surface form Disambiguated ID Type / Status
Subject Termessos E95315 entity
Predicate materialRemains P16216 FINISHED
Object stone masonry structures 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: stone masonry structures | Statement: [Termessos, materialRemains, stone masonry structures]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: materialRemains
Context triple: [Termessos, materialRemains, stone masonry structures]
  • A. materialUsed
    Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
  • B. materialProvidedFor
    Indicates that one entity supplies or makes available a material for use, processing, or incorporation by another entity or purpose.
  • C. material
    Indicates that one entity is physically composed of, made from, or constructed using the substance or material represented by the other entity.
  • D. hasRemainsOf chosen
    Indicates that one entity physically contains, preserves, or is associated with the leftover physical traces or remnants of another entity.
  • E. materialInvolved
    Indicates that a particular material participates in, is used by, or is otherwise involved in the referenced process, event, or relationship.
  • 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_69b3453c2a0c8190926b574c90766db9 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b35569b3388190bdef2568f5dc04ce completed March 13, 2026, 12:08 a.m.
PD Predicate disambiguation batch_69b34f6078cc8190831b89f404198cc5 completed March 12, 2026, 11:42 p.m.
Created at: March 12, 2026, 11:30 p.m.