Triple
T14025735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exercise Varuna |
E337450
|
entity |
| Predicate | involvesAssetType |
P15055
|
FINISHED |
| Object | surface combatants |
—
|
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: surface combatants | Statement: [Exercise Varuna, involvesAssetType, surface combatants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesAssetType Context triple: [Exercise Varuna, involvesAssetType, surface combatants]
-
A.
assetType
chosen
Indicates the specific category or classification of an asset within a broader asset framework or system.
-
B.
ownsAssetType
Indicates that an entity possesses ownership rights over an asset of a specified type.
-
C.
coversAssetClass
Indicates that one entity (such as a product, service, or policy) includes, applies to, or provides coverage for a specified asset class.
-
D.
hasFinancialInstrumentType
Indicates that an entity is associated with, or classified by, a specific type or category of financial instrument.
-
E.
assetOwnerType
Indicates the type or category of entity that owns or holds the asset.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fa6ca7481908976ce748a1957b1 |
completed | April 14, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.