Triple

T4116447
Position Surface form Disambiguated ID Type / Status
Subject Flag of Gibraltar E90302 entity
Predicate lowerBandWidth P54728 FINISHED
Object one third of flag height 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: one third of flag height | Statement: [Flag of Gibraltar, lowerBandWidth, one third of flag height]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lowerBandWidth
Context triple: [Flag of Gibraltar, lowerBandWidth, one third of flag height]
  • A. lowerLimit
    Indicates that one value serves as the minimum or smallest allowable bound or threshold for another value or range.
  • B. supportsBandwidths
    Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
  • C. usesChannelBandwidth
    Indicates that one entity consumes or occupies a portion of the available bandwidth on a communication channel.
  • D. lowerValueIndicates
    Indicates that a smaller numerical value of a property or measurement corresponds to a greater degree, better outcome, or stronger presence of the relevant characteristic.
  • E. transmissionBand
    Indicates the specific frequency range or band over which a signal, wave, or transmission is carried or allowed to pass.
  • 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_69aed95c080881908125e30c5dcdc6f8 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af03d7240c8190a64dcbc669772808 completed March 9, 2026, 5:31 p.m.
PD Predicate disambiguation batch_69af0183eb84819087d7184de28f5514 completed March 9, 2026, 5:21 p.m.
PDg Predicate description generation batch_69af03d5cce88190ad53bc6cfe10b21e completed March 9, 2026, 5:31 p.m.
Created at: March 9, 2026, 3:41 p.m.