Triple
T36767894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Status of Forces Agreement |
E908393
|
entity |
| Predicate | oftenConcludedUnder |
P145748
|
FINISHED |
| Object | bilateral treaty framework |
—
|
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: bilateral treaty framework | Statement: [Status of Forces Agreement, oftenConcludedUnder, bilateral treaty framework]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenConcludedUnder Context triple: [Status of Forces Agreement, oftenConcludedUnder, bilateral treaty framework]
-
A.
wasConcludedUnder
chosen
Indicates that an agreement, decision, or process was finalized according to, or within the framework of, a specific set of conditions, rules, authority, or context.
-
B.
concludedWith
Indicates that an event, process, or interaction ended or was finalized by a specific outcome, action, or state.
-
C.
concluded
Indicates that an entity has brought an event, process, discussion, or agreement to an end, often after reaching a decision or final judgment.
-
D.
concludedBy
Indicates that an event, process, or state is brought to an end or finalized by a specific agent or entity.
-
E.
concludesIn
Indicates that an event, process, or action ends or reaches its final state within a specified time, place, 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 3, 2026, 4:12 p.m.