Triple
T2128043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manolin |
E46468
|
entity |
| Predicate | appearsInLanguageVersion |
P31935
|
FINISHED |
| Object | English translation |
—
|
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 translation | Statement: [Manolin, appearsInLanguageVersion, English translation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInLanguageVersion Context triple: [Manolin, appearsInLanguageVersion, English translation]
-
A.
requiresLanguageVersion
Indicates that one entity depends on or must use a specific version of a language in order to function or be considered valid.
-
B.
alsoAvailableInVersion
chosen
Indicates that the same item, feature, or content is offered in another specified version or edition.
-
C.
presentedInLanguage
Indicates that something (such as content, information, or a work) is expressed or made available using a particular language.
-
D.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
E.
versionOf
Indicates that one entity is a specific form, edition, or variant derived from or corresponding to 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbb75033881909b16659fc73945ef |
completed | March 7, 2026, 5:45 a.m. |
| PD | Predicate disambiguation | batch_69abb7bd86cc8190938ef06c1ed6d969 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.