Triple
T29984475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Ancón |
E761691
|
entity |
| Predicate | signedByRepresentativeOfChile |
P6229
|
FINISHED |
| Object | Jovino Novoa |
—
|
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: Jovino Novoa | Statement: [Treaty of Ancón, signedByRepresentativeOfChile, Jovino Novoa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedByRepresentativeOfChile Context triple: [Treaty of Ancón, signedByRepresentativeOfChile, Jovino Novoa]
-
A.
signedByRepresentativeOf
chosen
Indicates that an item (such as a document or agreement) has been signed on behalf of a party by that party’s authorized representative.
-
B.
signedUnderChancellor
Indicates that a document or agreement was formally signed under the authority, oversight, or tenure of a specific chancellor.
-
C.
signatoryGovernment
Indicates that a government is a formal signer or ratifying party to an agreement, treaty, or similar binding instrument.
-
D.
wasSignatoryOf
Indicates that an entity formally signed or endorsed a specific document, agreement, or treaty as a participating party.
-
E.
signatoryDiplomat
Indicates that a diplomat is an official signatory to an agreement, treaty, or formal document.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f678dc12c481909e88cb5cf37d5d29 |
completed | May 2, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:36 p.m.