Triple

T16782581
Position Surface form Disambiguated ID Type / Status
Subject Tripylon (Central Palace) foundations E407891 entity
Predicate roleInSitePlan P79109 FINISHED
Object central circulation hub 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: central circulation hub | Statement: [Tripylon (Central Palace) foundations, roleInSitePlan, central circulation hub]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInSitePlan
Context triple: [Tripylon (Central Palace) foundations, roleInSitePlan, central circulation hub]
  • A. plannedRole
    Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
  • B. roleInUrbanPlan
    Indicates the specific function, responsibility, or position an entity holds within an urban planning context or scheme.
  • C. siteRole chosen
    Indicates the specific function, responsibility, or position an entity holds within a particular site or location.
  • D. architecturalRole
    Indicates the functional or design-related role that one entity plays within the structure, layout, or organization of another entity.
  • E. roleInCommandStructure
    Indicates that one entity holds a specific position or function within the hierarchical command structure of another entity or organization.
  • 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_69d8839270588190886720d9519bbf8f completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3b217b2108190bbba262a3b324509 completed April 18, 2026, 4:32 p.m.
PD Predicate disambiguation batch_69e319cf691c819083e39225f5777ef0 completed April 18, 2026, 5:42 a.m.
Created at: April 10, 2026, 5:22 a.m.