Triple
T32318835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICAO Chapter 4 |
E825714
|
entity |
| Predicate | usesMeasurementPoints |
P182780
|
FINISHED |
| Object | flyover |
—
|
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 | Statement: [ICAO Chapter 4, usesMeasurementPoints, flyover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMeasurementPoints Context triple: [ICAO Chapter 4, usesMeasurementPoints, flyover]
-
A.
hasMeasurement
Indicates that an entity is associated with a specific measured value, often including a unit or measurement context.
-
B.
containsMeasure
Indicates that one entity includes or encompasses a specific measure or quantitative component as part of its content or structure.
-
C.
enabledMeasurementOf
Indicates that one entity made it possible or allowed another entity to perform or obtain a specific measurement.
-
D.
supportsUserDefinedMeasurements
Indicates that an entity allows users to create, configure, and use their own custom measurement definitions or metrics.
-
E.
hasMeasurementRole
Indicates that an entity participates in a measurement activity in a specific functional role (e.g., as the measurer, instrument, or measured subject).
- 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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7908ec35881909a42f954fb9fa16e |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78fd3fd888190b7db0b563f298585 |
completed | May 3, 2026, 6:11 p.m. |
Created at: May 1, 2026, 12:46 a.m.