Triple
T28962317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cómo Dónde y Cuándo |
E731934
|
entity |
| Predicate | titleInEnglishTransliteration |
P52223
|
FINISHED |
| Object | Como Donde y Cuando |
—
|
NE NERFINISHED |
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: Como Donde y Cuando | Statement: [Cómo Dónde y Cuándo, titleInEnglishTransliteration, Como Donde y Cuando]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleInEnglishTransliteration Context triple: [Cómo Dónde y Cuándo, titleInEnglishTransliteration, Como Donde y Cuando]
-
A.
titleInEnglish
Indicates that an entity’s title or name is given in the English language.
-
B.
titleInLanguage
Indicates that a specific title or name is expressed in a particular language.
-
C.
titleInLatinScript
chosen
Indicates that the title of an entity is written or represented using a Latin-based writing system.
-
D.
hasTitleInTransliteration
Indicates that an entity has a specific title represented in a transliterated form from another writing system.
-
E.
translationTitle
Indicates that one entity is the title assigned to a translated version of another entity (such as a work, document, or text).
- 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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 28, 2026, 8:50 a.m.