Triple
T27167390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viejo Mundo |
E682814
|
entity |
| Predicate | seUsaEn |
P161928
|
FINISHED |
| Object | contexto colonial europeo |
—
|
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: contexto colonial europeo | Statement: [Viejo Mundo, seUsaEn, contexto colonial europeo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seUsaEn Context triple: [Viejo Mundo, seUsaEn, contexto colonial europeo]
-
A.
seUsaEn
chosen
Indicates that something is used or employed within, in, or for a particular context, place, or purpose.
-
B.
languageOfUSVersion
Indicates that one entity is the language used in the U.S. version of another entity (such as a work, product, or edition).
-
C.
hasUSAN
Indicates that an entity has a specified United States Adopted Name (USAN), typically a nonproprietary name assigned to a pharmaceutical substance.
-
D.
isInEnglishSpeakingCountry
Indicates that an entity is located in, associated with, or belongs to a country where English is an official or primary language of communication.
-
E.
languageUse
Indicates the language or languages an entity uses for communication, expression, or interaction.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62543fd78819093ccb2b5844dfd72 |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 9:21 a.m.