Triple
T21824373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Support Group of Argentina, Brazil, Peru, and Uruguay |
E538811
|
entity |
| Predicate | roleRelativeToContadoraGroup |
P133192
|
FINISHED |
| Object | complementary |
—
|
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: complementary | Statement: [Support Group of Argentina, Brazil, Peru, and Uruguay, roleRelativeToContadoraGroup, complementary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleRelativeToContadoraGroup Context triple: [Support Group of Argentina, Brazil, Peru, and Uruguay, roleRelativeToContadoraGroup, complementary]
-
A.
roleOfGroup
Indicates the function, responsibility, or position that a group holds within a broader context or structure.
-
B.
roleInParentGroup
Indicates the specific function, position, or responsibility an entity holds within its parent group or organization.
-
C.
roleWithCEP
Indicates that an entity holds a specific role or function that is associated with a defined Contextualized Event or Process (CEP).
-
D.
roleOnPern
Indicates the specific function, position, or duty an entity holds within the context of Pern.
-
E.
roleWith
chosen
Indicates that one entity holds or performs a particular role in relation to 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_69e0c475038c8190abb9b1a20eb8ff50 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f091307d408190a92b65c3f39682a8 |
completed | April 28, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:54 p.m.