Triple
T6656920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Decisive Storm |
E150968
|
entity |
| Predicate | groundOperations |
P60270
|
FINISHED |
| Object | limited or indirect |
—
|
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: limited or indirect | Statement: [Operation Decisive Storm, groundOperations, limited or indirect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groundOperations Context triple: [Operation Decisive Storm, groundOperations, limited or indirect]
-
A.
groundService
Indicates that one entity provides ground-based operational support or services to another entity, typically in a transportation or logistics context.
-
B.
ground
Indicates that one entity is in contact with or supported by the ground or a ground-like surface.
-
C.
groundComponent
Indicates that one entity serves as a foundational or base part upon which another entity is built, attached, or functionally dependent.
-
D.
hasLandOperations
chosen
Indicates that an entity conducts or is responsible for activities, services, or operations carried out on land.
-
E.
hasRunwayOperations
Indicates that an entity conducts or is involved in operational activities on an airport runway, such as takeoffs, landings, or related ground movements.
- 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9d53848190ac75523c157249c6 |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:01 p.m.