Triple
T27454685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 3L |
E692554
|
entity |
| Predicate | isMarkedAccordingTo |
P162411
|
FINISHED |
| Object | ICAO runway marking standards |
—
|
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: ICAO runway marking standards | Statement: [Runway 3L, isMarkedAccordingTo, ICAO runway marking standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMarkedAccordingTo Context triple: [Runway 3L, isMarkedAccordingTo, ICAO runway marking standards]
-
A.
wasMarkedBy
Indicates that an entity bears a mark, sign, or indication that was applied or caused by another entity.
-
B.
usedToMark
Indicates that one entity serves as a marker, label, or indicator for another entity.
-
C.
usedMark
Indicates that one entity has employed or applied a particular mark, symbol, or indicator in some context or action.
-
D.
hasProofMark
Indicates that an entity bears a specific proof mark signifying it has passed an official test or inspection.
-
E.
hasMarker
Indicates that one entity possesses, is associated with, or is identified by a specific marker.
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62dc89bfc81909987840a660f709f |
completed | May 2, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 12:48 p.m.