Triple
T563161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish–Romanian alliance |
E13496
|
entity |
| Predicate | focusOfDefense |
P8671
|
FINISHED |
| Object | eastern borders of Poland |
—
|
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: eastern borders of Poland | Statement: [Polish–Romanian alliance, focusOfDefense, eastern borders of Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusOfDefense Context triple: [Polish–Romanian alliance, focusOfDefense, eastern borders of Poland]
-
A.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
B.
missionFocus
chosen
Indicates that an entity’s primary attention, effort, or resources are directed toward a particular mission, goal, or objective.
-
C.
defender
Indicates a relationship where one entity protects, guards, or supports another entity against threats, attacks, or criticism.
-
D.
casusBelli
Indicates a relationship where one entity serves as the cause, justification, or pretext for another entity to initiate conflict or war.
-
E.
defenseResult
Indicates the outcome or consequence of a defensive action or strategy in response to an attack or threat.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49a712bc48190ba298b3c76ab11cc |
completed | March 1, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69a494c044648190a98589ab18935216 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.