Triple
T1995008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Ladbroke |
E43337
|
entity |
| Predicate | forceTypeUsed |
P1062
|
FINISHED |
| Object | glider infantry |
—
|
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: glider infantry | Statement: [Operation Ladbroke, forceTypeUsed, glider infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forceTypeUsed Context triple: [Operation Ladbroke, forceTypeUsed, glider infantry]
-
A.
forceType
chosen
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
-
B.
forcedBy
Indicates that an entity is compelled or coerced into an action or state by another entity.
-
C.
forceDirection
Indicates the direction in which a force is applied or exerted in the relationship between entities.
-
D.
inForceUntil
Indicates that a condition, rule, or agreement remains valid and operative up to a specified time or event.
-
E.
formationType
Indicates the specific structural or organizational configuration in which something is arranged, created, or formed.
- 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_69a88714cf2c819081644be450b8356e |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8ee02dc81908fec9fd8df7a4f40 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb79ad6888190be99943a9c73cf3e |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:37 p.m.