Triple

T29045685
Position Surface form Disambiguated ID Type / Status
Subject ICAO Chapter 8 E735129 entity
Predicate usesMeasurementPoint P52567 FINISHED
Object flyover noise measurement point 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: flyover noise measurement point | Statement: [ICAO Chapter 8, usesMeasurementPoint, flyover noise measurement point]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesMeasurementPoint
Context triple: [ICAO Chapter 8, usesMeasurementPoint, flyover noise measurement point]
  • A. enabledMeasurementOf
    Indicates that one entity made it possible or allowed another entity to perform or obtain a specific measurement.
  • B. hasMeasurement
    Indicates that an entity is associated with a specific measured value, often including a unit or measurement context.
  • C. containsMeasure
    Indicates that one entity includes or encompasses a specific measure or quantitative component as part of its content or structure.
  • D. usesMeasurementTechnique chosen
    Indicates that an entity performs, applies, or relies on a specified measurement technique to obtain quantitative or qualitative data.
  • E. usesMeasureDomain
    Indicates that one entity employs or relies on a particular measurement domain or measurement framework as the basis for its values or evaluations.
  • 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_69f077e64b88819094d37bdbca8191b3 completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69f6ffbad8848190867c2988c0ceb84f completed May 3, 2026, 7:56 a.m.
PD Predicate disambiguation batch_69f6fc53f4f881908dcc698687bbb64d completed May 3, 2026, 7:42 a.m.
Created at: April 28, 2026, 10:05 a.m.