Triple

T15487255
Position Surface form Disambiguated ID Type / Status
Subject Puente de la Exposición E377077 entity
Predicate hasArchitecturalDiscipline P118425 FINISHED
Object bridge 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: bridge architecture | Statement: [Puente de la Exposición, hasArchitecturalDiscipline, bridge architecture]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasArchitecturalDiscipline
Context triple: [Puente de la Exposición, hasArchitecturalDiscipline, bridge architecture]
  • A. architecturalWork
    Indicates that one entity is an architectural creation (such as a building or structure) designed or realized by another entity.
  • B. architecturalRole
    Indicates the functional or design-related role that one entity plays within the structure, layout, or organization of another entity.
  • C. hasRelationToArchitect
    Indicates that one entity has a specified relationship or association with an architect.
  • D. hasArchitectRole
    Indicates that an entity holds or fulfills the role or function of an architect in relation to another entity or project.
  • E. hasArchitecturalFeature
    Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
  • 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_69d85cd21dcc81908646251b1c26ea00 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03f8f71a08190a440ff19dcc65312 completed April 16, 2026, 1:46 a.m.
PD Predicate disambiguation batch_69ded2874b788190999158e0f043be21 completed April 14, 2026, 11:49 p.m.
PDg Predicate description generation batch_69ded5deee00819099fa3e43313312e1 completed April 15, 2026, 12:03 a.m.
Created at: April 10, 2026, 3:48 a.m.