Triple
T29316323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Amud Anan |
E743389
|
entity |
| Predicate | groundInvasion |
P113615
|
FINISHED |
| Object | no large-scale ground invasion launched |
—
|
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: no large-scale ground invasion launched | Statement: [Operation Amud Anan, groundInvasion, no large-scale ground invasion launched]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groundInvasion Context triple: [Operation Amud Anan, groundInvasion, no large-scale ground invasion launched]
-
A.
ground
Indicates that one entity is in contact with or supported by the ground or a ground-like surface.
-
B.
methodOfInvasion
chosen
Indicates the specific way or technique by which an invasion is carried out.
-
C.
landAction
Indicates an action in which an entity comes down to and makes contact with a surface or ground, typically concluding a movement through air or space.
-
D.
invade
Indicates entering another entity’s territory or domain, typically by force or without permission, in order to take control or exert dominance.
-
E.
usesGroundFor
Indicates that one entity makes functional or practical use of a particular ground, surface, or land area for its activities or purposes.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665ec3ee481909ae35e76899a7056 |
completed | May 2, 2026, 9 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:20 p.m.