Triple
T27167388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viejo Mundo |
E682814
|
entity |
| Predicate | seUsaEn |
P161928
|
FINISHED |
| Object | historiografía europea |
—
|
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: historiografía europea | Statement: [Viejo Mundo, seUsaEn, historiografía europea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seUsaEn Context triple: [Viejo Mundo, seUsaEn, historiografía europea]
-
A.
languageOfUSVersion
Indicates that one entity is the language used in the U.S. version of another entity (such as a work, product, or edition).
-
B.
hasUSAN
Indicates that an entity has a specified United States Adopted Name (USAN), typically a nonproprietary name assigned to a pharmaceutical substance.
-
C.
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.
-
D.
languageUse
Indicates the language or languages an entity uses for communication, expression, or interaction.
-
E.
USProvides
Indicates that the United States supplies, furnishes, or makes available something (such as aid, resources, services, or support) to another entity.
- F. None of above. chosen
Provenance (4 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_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fa35ac48190890102c348ed81a0 |
completed | May 2, 2026, 4 p.m. |
Created at: April 27, 2026, 9:21 a.m.