Triple

T11916807
Position Surface form Disambiguated ID Type / Status
Subject Grote Zaal E283544 entity
Predicate relativeSizeWithinComplex P94423 FINISHED
Object largest concert hall in TivoliVredenburg 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: largest concert hall in TivoliVredenburg | Statement: [Grote Zaal, relativeSizeWithinComplex, largest concert hall in TivoliVredenburg]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relativeSizeWithinComplex
Context triple: [Grote Zaal, relativeSizeWithinComplex, largest concert hall in TivoliVredenburg]
  • A. relativeSizeWithinSite chosen
    Indicates the comparative size relationship of one entity to another within the same site or local context.
  • B. relativeSizeOnTethys
    Indicates how the size of one entity compares to another specifically in the context of Tethys.
  • C. relativeLength
    Indicates a comparative relationship between entities based on how long they are relative to one another.
  • D. hasRelativeSize
    Indicates that one entity’s size is being compared to another entity’s size, expressing a relative rather than absolute magnitude.
  • E. relativeSizeInFleet
    Indicates the comparative size or capacity of an entity relative to other entities within the same fleet.
  • 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_69d6ab2c07e88190ba13b0d21fd6cf33 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8e8deb14881909b65a1f159aec65f completed April 10, 2026, 12:11 p.m.
PD Predicate disambiguation batch_69d8bb3632ac8190b13e53c2b5db7125 completed April 10, 2026, 8:56 a.m.
Created at: April 8, 2026, 9:44 p.m.