Triple

T35166580
Position Surface form Disambiguated ID Type / Status
Subject Blobitecture E1015418 entity
Predicate oftenUsesMaterial P1272 FINISHED
Object reinforced concrete 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: reinforced concrete | Statement: [Blobitecture, oftenUsesMaterial, reinforced concrete]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: oftenUsesMaterial
Context triple: [Blobitecture, oftenUsesMaterial, reinforced concrete]
  • A. materialUsed chosen
    Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
  • B. usesMaterialBy
    Indicates that one entity makes use of or employs a material that is provided, specified, or created by another entity.
  • C. usesSupportMaterial
    Indicates that an entity relies on or incorporates additional supporting materials or resources to carry out an action or fulfill a function.
  • D. usesFolkMaterial
    Indicates that one entity incorporates or draws upon traditional folk materials, such as melodies, stories, or motifs, in relation to another entity.
  • E. traditionalMaterial
    Indicates that something is made from, incorporates, or is characterized by materials associated with long-established or customary practices.
  • 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_69f76ddbfde081908bffc91572368289 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fd7b0503a08190ba07338365b6fcc9 completed May 8, 2026, 5:56 a.m.
PD Predicate disambiguation batch_69fd7a9733dc81909199f453c0cc2bc1 completed May 8, 2026, 5:54 a.m.
Created at: May 3, 2026, 4:02 p.m.