Triple
T16149956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LCL |
E391884
|
entity |
| Predicate | providesTranslationIn |
P52478
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [LCL, providesTranslationIn, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesTranslationIn Context triple: [LCL, providesTranslationIn, English]
-
A.
hasTranslation
Indicates that one entity is a translation or translated version of another entity in a different language.
-
B.
translatedIn
Indicates that a work, text, or content has been rendered from its original language into another specified language or linguistic form.
-
C.
languageOfTranslations
chosen
Indicates that one entity is the language into which another entity (such as a text or work) has been translated.
-
D.
canTranslateBetween
Indicates that an entity has the ability to translate or convert information accurately between two specified languages, formats, or representation systems.
-
E.
translationOn
Indicates that one entity is a translation of another entity, typically expressing the same content in a different language or linguistic form.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d9724808190a8332987583a345a |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.