Triple
T36039696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO OF-9 |
E1042504
|
entity |
| Predicate | usedForInteroperability |
P98
|
FINISHED |
| Object | joint operations rank comparison |
—
|
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 operations rank comparison | Statement: [NATO OF-9, usedForInteroperability, joint operations rank comparison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForInteroperability Context triple: [NATO OF-9, usedForInteroperability, joint operations rank comparison]
-
A.
isDesignedForInteroperability
Indicates that something is intended or configured to work seamlessly and compatibly with other systems, components, or standards.
-
B.
interoperabilityWith
Indicates that one system, component, or standard can effectively exchange and use information or services with another.
-
C.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
D.
usedInternally
Indicates that something is utilized within an organization, system, or component itself rather than being exposed or provided for external use.
-
E.
isIntendedForUseBy
Indicates that something is designed, meant, or purposed to be used by a particular entity or group.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 3, 2026, 4:07 p.m.