Triple
T8914757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Rapid Deployable Corps Spain |
E212268
|
entity |
| Predicate | isMultinational |
P8760
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NATO Rapid Deployable Corps Spain, isMultinational, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMultinational Context triple: [NATO Rapid Deployable Corps Spain, isMultinational, true]
-
A.
underlyingIsMultinational
chosen
Indicates that the underlying entity operates in or is registered across multiple countries as a multinational organization.
-
B.
multiNationalState
Indicates a state whose population is composed of multiple distinct national or ethnic groups under a single political authority.
-
C.
isInternational
Indicates that something has a connection to, involves, or extends across more than one country.
-
D.
isMultilateral
Indicates that a relationship, agreement, or interaction involves three or more distinct parties or entities participating together.
-
E.
isMultilingual
Indicates that an entity can understand and/or communicate in multiple languages.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc660e620c8190b02b9843c8f02bfa |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.