Triple
T25563525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNTAES |
E640775
|
entity |
| Predicate | implementedAgreement |
P134708
|
FINISHED |
| Object | Erdut Agreement |
—
|
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: Erdut Agreement | Statement: [UNTAES, implementedAgreement, Erdut Agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedAgreement Context triple: [UNTAES, implementedAgreement, Erdut Agreement]
-
A.
implementsAgreementWith
chosen
Indicates that one party carries out or fulfills the terms of an agreement made with another party.
-
B.
agreementInvoked
Indicates that a formal agreement or contract has been activated, called upon, or put into effect between the related entities.
-
C.
confirmedAgreementBetween
Indicates that a previously proposed agreement between two or more parties has been formally verified, accepted, and is now recognized as valid.
-
D.
basedOnAgreementWith
Indicates that something exists, is done, or is determined on the basis of a prior agreement or accord between the involved parties.
-
E.
agreementOutcome
Indicates the result or consequence that follows from reaching or failing to reach an agreement between 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8fa9fa0819098761026a7f9353d |
completed | May 2, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 3:47 p.m.