Triple
T563155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish–Romanian alliance |
E13496
|
entity |
| Predicate | typeOfAgreement |
P405
|
FINISHED |
| Object | defensive treaty |
—
|
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: defensive treaty | Statement: [Polish–Romanian alliance, typeOfAgreement, defensive treaty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAgreement Context triple: [Polish–Romanian alliance, typeOfAgreement, defensive treaty]
-
A.
typeOfContract
chosen
Indicates the specific kind or category of contractual agreement that applies between the related entities.
-
B.
basedOnAgreementWith
Indicates that something exists, is done, or is determined on the basis of a prior agreement or accord between the involved parties.
-
C.
agreement
Indicates that two or more parties mutually consent to and accept shared terms, conditions, or understandings.
-
D.
typeOfRight
Indicates the specific category or nature of a right that is held, exercised, or assigned in a given context.
-
E.
typeOfNegotiation
Indicates the specific kind or category of negotiation process that characterizes the interaction between the involved parties.
- 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.