Triple
T29380987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Rapid Deployable Corps – Turkey |
E745133
|
entity |
| Predicate | hostNationSupportProvidedBy |
P75190
|
FINISHED |
| Object | Turkey |
—
|
NE NERFINISHED |
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: Turkey | Statement: [NATO Rapid Deployable Corps – Turkey, hostNationSupportProvidedBy, Turkey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostNationSupportProvidedBy Context triple: [NATO Rapid Deployable Corps – Turkey, hostNationSupportProvidedBy, Turkey]
-
A.
hostNationSupport
chosen
Indicates that one nation provides logistical, operational, or resource support within its territory to assist the activities or presence of another nation.
-
B.
hostNationBase
Indicates that one nation serves as the host country for a military or strategic base belonging to another entity.
-
C.
hostNationCapital
Indicates that a city serves as the capital of a particular host nation.
-
D.
hostNationStatus
Indicates that an entity holds the official status of being the host nation for a particular event, activity, or arrangement.
-
E.
hostNationRole
Indicates the role or capacity in which a nation serves as the host in a particular event, activity, or context.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669ce489081909e5b3187581daa29 |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:35 p.m.