Triple
T25161614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sistema Interamericano de Derechos Humanos |
E626453
|
entity |
| Predicate | regiónCobertura |
P19200
|
FINISHED |
| Object | continente americano |
—
|
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: continente americano | Statement: [Sistema Interamericano de Derechos Humanos, regiónCobertura, continente americano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regiónCobertura Context triple: [Sistema Interamericano de Derechos Humanos, regiónCobertura, continente americano]
-
A.
regionCoverage
chosen
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
B.
geographicCoverageType
Indicates the type or nature of the geographic area that something covers or applies to.
-
C.
hasAreaOfCoverage
Indicates that an entity provides services, influence, or applicability within a specified geographic or conceptual region.
-
D.
geographicAreaOfSupport
Indicates the geographic region or area within which support, assistance, or services are provided or applicable.
-
E.
mapCoverage
Indicates the extent or area that is represented, covered, or included by a particular map.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f46b8d45548190a5bdb4fba1d3ba4e |
completed | May 1, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:31 a.m.