Triple
T23062451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO (as supported asset) |
E574939
|
entity |
| Predicate | supportedAssetDomain |
P107023
|
FINISHED |
| Object | joint air-land operations |
—
|
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: joint air-land operations | Statement: [NATO (as supported asset), supportedAssetDomain, joint air-land operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedAssetDomain Context triple: [NATO (as supported asset), supportedAssetDomain, joint air-land operations]
-
A.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
-
B.
supportsDomainType
chosen
Indicates that one entity is capable of handling, operating with, or being applicable to a specified domain type.
-
C.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
D.
supportsCustomDomain
Indicates that an entity provides the capability to use or configure a custom domain name instead of a default or system-assigned domain.
-
E.
supportedNetwork
Indicates that one entity (such as a device, service, or application) is compatible with, operates on, or is designed to work over a specified network or type of network.
- 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_69e245bd6e4c8190bb8942245b68cad5 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f189a0c3c881909f137ad511c216ac |
completed | April 29, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:55 p.m.