Triple
T29811282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neutrality Treaty |
E756969
|
entity |
| Predicate | hasCounterpartTreaty |
P123310
|
FINISHED |
| Object | Panama Canal Treaty of 1977 |
—
|
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: Panama Canal Treaty of 1977 | Statement: [Neutrality Treaty, hasCounterpartTreaty, Panama Canal Treaty of 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCounterpartTreaty Context triple: [Neutrality Treaty, hasCounterpartTreaty, Panama Canal Treaty of 1977]
-
A.
treatyRelation
Indicates that there exists a formal treaty-based relationship or agreement between the referenced entities.
-
B.
hasMainTreaty
Indicates that one entity is the primary or principal treaty associated with another entity.
-
C.
hasTreatySettlementWith
chosen
Indicates the existence of a formal treaty-based agreement or settlement between two parties.
-
D.
treatyOf
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
-
E.
treatySignedWith
Indicates that a formal treaty or agreement has been officially signed between two 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a00ab25c5b48190ad07ff508392ef56 |
completed | May 10, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_6a00a8a5cfc48190bbe97fb2bbd1b947 |
completed | May 10, 2026, 3:47 p.m. |
Created at: April 29, 2026, 5:24 p.m.