Triple
T34653625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Throat of Fire |
E889910
|
entity |
| Predicate | hasTranslationEquivalent |
P200246
|
FINISHED |
| Object | Tungurahua |
—
|
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: Tungurahua | Statement: [Throat of Fire, hasTranslationEquivalent, Tungurahua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTranslationEquivalent Context triple: [Throat of Fire, hasTranslationEquivalent, Tungurahua]
-
A.
hasTranslation
Indicates that one entity is a translation or translated version of another entity in a different language.
-
B.
hasTranslated
Indicates that one entity has rendered the content of another entity from one language into a different language.
-
C.
hasTranslationBase
Indicates that one entity serves as the original source or base text from which the other entity is translated.
-
D.
hasCommonTranslationLanguage
Indicates that two entities share at least one language into which both can be or have been translated.
-
E.
hasTranslationComponent
Indicates that one entity includes or is associated with a component responsible for translating or converting content from one form or language to another.
- 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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff7c96e6dc8190b89554480ebcea39 |
completed | May 9, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69ff7c2381748190ad9a2176e0e478cd |
completed | May 9, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69ff7c96036c8190bfae5ec9b5a1965f |
completed | May 9, 2026, 6:27 p.m. |
Created at: May 1, 2026, 2:04 a.m.