Triple
T23939570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triple Alliance forces |
E602742
|
entity |
| Predicate | formedByTreatyWith |
P99458
|
FINISHED |
| Object | Empire of Brazil |
—
|
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: Empire of Brazil | Statement: [Triple Alliance forces, formedByTreatyWith, Empire of Brazil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedByTreatyWith Context triple: [Triple Alliance forces, formedByTreatyWith, Empire of Brazil]
-
A.
treatyOf
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
-
B.
treatySignedWith
Indicates that a formal treaty or agreement has been officially signed between two parties.
-
C.
cededByTreaty
Indicates that control or ownership of one entity was formally transferred to another entity as a result of a treaty or formal agreement.
-
D.
independenceTreaty
Indicates that a formal treaty establishes or recognizes political independence between the involved parties.
-
E.
establishedByTreatyOrAct
chosen
Indicates that the relationship or entity was formally created, defined, or authorized through a specific treaty or legislative act.
- 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1cfa40398819095e24521f3bf8622 |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:08 p.m.