Triple
T296284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-17 Globemaster III |
E6098
|
entity |
| Predicate | canOperateFrom |
P6602
|
FINISHED |
| Object | short runways |
—
|
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: short runways | Statement: [C-17 Globemaster III, canOperateFrom, short runways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canOperateFrom Context triple: [C-17 Globemaster III, canOperateFrom, short runways]
-
A.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
-
B.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
C.
operatedFrom
chosen
Indicates that an entity conducted its activities or operations starting from or based at a particular location or source.
-
D.
operatesBy
Indicates that an entity performs its function, action, or process through the use or application of another entity (e.g., a method, mechanism, or principle).
-
E.
canMake
Indicates that one entity has the ability or capacity to create, produce, or assemble another entity.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea4778cc8190be7b648a82542891 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e937af888190a0960708f09ae033 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.