Triple
T5044804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doce cuentos peregrinos |
E113635
|
entity |
| Predicate | periodOfWriting |
P1143
|
FINISHED |
| Object | approximately 18 years |
—
|
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: approximately 18 years | Statement: [Doce cuentos peregrinos, periodOfWriting, approximately 18 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfWriting Context triple: [Doce cuentos peregrinos, periodOfWriting, approximately 18 years]
-
A.
writtenDuring
chosen
Indicates that the creation or authorship of something took place within a specified time period or historical event.
-
B.
literaryPeriodOfWork
Indicates the literary period or movement to which a particular work belongs.
-
C.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
D.
laterWrittenIn
Indicates that one text or version was written at a later time than another, establishing a chronological order between the writings.
-
E.
wrote
Indicates that an entity is the author or creator of a written work involving another entity.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73fd81788190b7799f519277119a |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.