Triple
T17837729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 10/28 |
E445435
|
entity |
| Predicate | usedUnderCondition |
P61769
|
FINISHED |
| Object | various wind conditions |
—
|
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: various wind conditions | Statement: [Runway 10/28, usedUnderCondition, various wind conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedUnderCondition Context triple: [Runway 10/28, usedUnderCondition, various wind conditions]
-
A.
holdsUnderCondition
chosen
Indicates that one fact, rule, or relationship remains valid only when a specified condition or set of conditions is satisfied.
-
B.
usedCondition
Indicates that one entity is employed or applied under a particular state, requirement, or circumstance defined by another entity.
-
C.
isUsedUnder
Indicates that one entity is utilized or applied within the context, conditions, or framework defined by another entity.
-
D.
usedInCase
Indicates that something (such as an item, method, or piece of information) is employed or applied within a particular case or instance.
-
E.
presentCondition
Indicates that an entity currently has or exhibits a particular state, situation, or condition.
- 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48d28c14881909033abd09bbdb135 |
completed | April 19, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:16 a.m.