Triple
T1024107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Garden |
E22100
|
entity |
| Predicate | typeOfAdvance |
P23492
|
FINISHED |
| Object | armoured ground thrust |
—
|
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: armoured ground thrust | Statement: [Operation Garden, typeOfAdvance, armoured ground thrust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAdvance Context triple: [Operation Garden, typeOfAdvance, armoured ground thrust]
-
A.
advancedThrough
Indicates that an entity has progressed or moved forward within, or as a result of, a particular medium, stage, process, or pathway.
-
B.
mayAdvanceTo
Indicates that one entity is permitted or eligible to progress, move, or be promoted to another specified state, level, or position.
-
C.
developmentLevel
Indicates the degree or stage of progress, advancement, or maturity that something has reached in its growth or evolution.
-
D.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
E.
trainingLevel
Indicates the degree or stage of training or skill development that an entity has attained.
- F. None of above. chosen
Provenance (4 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7e28df08190b5be7794442a6f21 |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b72619cc8190932fdfa0c74dc055 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7a0d0308190a00192aa9062bdaa |
completed | March 1, 2026, 10:03 p.m. |
Created at: March 1, 2026, 7:41 p.m.