Triple
T19730478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olenya air base |
E473837
|
entity |
| Predicate | capableOfHandling |
P39122
|
FINISHED |
| Object | strategic bombers |
—
|
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: strategic bombers | Statement: [Olenya air base, capableOfHandling, strategic bombers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capableOfHandling Context triple: [Olenya air base, capableOfHandling, strategic bombers]
-
A.
isCapableOf
chosen
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
B.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
C.
capacityCategory
Indicates the classification of something based on the amount or volume it can hold, handle, or accommodate.
-
D.
hasPassengerHandling
Indicates that an entity is responsible for or involved in managing the processes and services related to handling passengers.
-
E.
designedToWithstand
Indicates that something has been intentionally created or engineered to resist, endure, or remain functional under specified conditions, forces, or stresses.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649fbeaf081909e9356229eaf84dd |
completed | April 20, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.