Triple
T3897390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish defense industry |
E90401
|
entity |
| Predicate | exportDestination |
P40218
|
FINISHED |
| Object | NATO member states |
—
|
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: NATO member states | Statement: [Polish defense industry, exportDestination, NATO member states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportDestination Context triple: [Polish defense industry, exportDestination, NATO member states]
-
A.
originalDestination
Indicates the initial or intended destination associated with an entity before any changes, rerouting, or redirection occur.
-
B.
attemptedDestination
Indicates that an entity made an effort to reach or go to a particular destination, regardless of whether the attempt was successful.
-
C.
portedTo
Indicates that something has been adapted or transferred from its original environment or platform to run or function on a different one.
-
D.
servedDestination
Indicates that a service or action is directed toward, or provided to, a particular destination.
-
E.
directedTo
chosen
Indicates that something is sent, aimed, or addressed toward a particular target or recipient.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.