Triple
T18489857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cumbres de las Américas |
E451789
|
entity |
| Predicate | participantesTípicos |
P7712
|
FINISHED |
| Object | jefes de Estado |
—
|
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: jefes de Estado | Statement: [Cumbres de las Américas, participantesTípicos, jefes de Estado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participantesTípicos Context triple: [Cumbres de las Américas, participantesTípicos, jefes de Estado]
-
A.
originalParticipantsType
Indicates the type or category of participants that were initially involved in an event, action, or relationship.
-
B.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
C.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
D.
typicalParty
chosen
Indicates that an entity is a usual, standard, or characteristic participant in a given type of event, situation, or relationship.
-
E.
typicalContributors
Indicates the entities that commonly or characteristically contribute to, or are responsible for, another entity or outcome.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d9d75081908e81fbccf6896bbc |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.