Triple
T18489922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cimeiras das Américas |
E451790
|
entity |
| Predicate | têmPeriodicidade |
P7407
|
FINISHED |
| Object | periódica |
—
|
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: periódica | Statement: [Cimeiras das Américas, têmPeriodicidade, periódica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: têmPeriodicidade Context triple: [Cimeiras das Américas, têmPeriodicidade, periódica]
-
A.
tienePeriodicidad
chosen
Indicates that something occurs, recurs, or is scheduled with a specific regular frequency or periodic pattern.
-
B.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
C.
periodizedAs
Indicates that something has been divided or organized into distinct time periods according to a particular periodization scheme.
-
D.
periodProperty
Indicates a temporal characteristic or attribute associated with a specific time period or interval.
-
E.
periodReception
Indicates a temporal relationship where one entity receives, hosts, or is associated with another during a specific time period or interval.
- 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.