Triple

T31593249
Position Surface form Disambiguated ID Type / Status
Subject Intze principle E806155 entity
Predicate typicalSupportSystem P207467 FINISHED
Object RC columns and bracing system 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: RC columns and bracing system | Statement: [Intze principle, typicalSupportSystem, RC columns and bracing system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalSupportSystem
Context triple: [Intze principle, typicalSupportSystem, RC columns and bracing system]
  • A. typeOfSupport
    Indicates the kind or category of assistance, help, or backing provided in a given context.
  • B. typicalSupportDuration
    Indicates the usual length of time that support or assistance is expected to be provided in this context.
  • C. typicalSupportSeriesRole
    Indicates the usual or characteristic role that an entity plays within a support series or sequence of related support activities.
  • D. providesSupportTo
    Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
  • E. IndependentSupportBase
    Indicates that one entity serves as a foundational, self-sufficient support structure for another, not relying on additional supports or connections.
  • 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_69f348d4891c8190b02bae3c8ecb68b7 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_6a037c9141dc819098d7fcc36e69882c completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a0379e7aa0c8190bdc9ee4d54fc821b completed May 12, 2026, 7:05 p.m.
PDg Predicate description generation batch_6a037c7ee0388190a29faeb5cdb0950a completed May 12, 2026, 7:16 p.m.
Created at: April 30, 2026, 10:29 p.m.