Triple
T29641900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Union Treaty |
E755883
|
entity |
| Predicate | wouldRetain |
P166603
|
FINISHED |
| Object | common president of the union |
—
|
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: common president of the union | Statement: [New Union Treaty, wouldRetain, common president of the union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wouldRetain Context triple: [New Union Treaty, wouldRetain, common president of the union]
-
A.
proposedToRetain
chosen
Indicates that one entity has suggested or decided to keep or continue maintaining another entity in its current role, state, or possession.
-
B.
mustRetain
Indicates that an entity is required to keep or preserve another entity and is not allowed to discard, delete, or release it.
-
C.
retained
Indicates that one entity keeps possession, control, or continued engagement of another entity over a period of time.
-
D.
canRetain
Indicates that one entity has the ability or permission to keep, hold, or maintain possession or control of another entity over time.
-
E.
keptWith
Indicates that one entity is stored, maintained, or held together in association with another entity.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 6:47 p.m.