Triple
T23939556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triple Alliance forces |
E602742
|
entity |
| Predicate | alliant |
P600
|
FINISHED |
| Object | Brazilian Army |
—
|
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: Brazilian Army | Statement: [Triple Alliance forces, alliant, Brazilian Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alliant Context triple: [Triple Alliance forces, alliant, Brazilian Army]
-
A.
alliedCompany
Indicates that one company has a formal alliance or partnership relationship with another company.
-
B.
alliedAgency
Indicates that one agency has a formal alliance or cooperative partnership relationship with another agency.
-
C.
alliedDesignation
Indicates that one entity assigns or recognizes an allied status or designation for another entity.
-
D.
alliance
chosen
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
E.
allianceUse
Indicates that one party makes use of, benefits from, or leverages an alliance or allied relationship with another party.
- 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.