Triple
T33979513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Velikaya knyazhna |
E871236
|
entity |
| Predicate | commonEnglishTranslation |
P31361
|
FINISHED |
| Object | Grand Duchess |
—
|
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: Grand Duchess | Statement: [Velikaya knyazhna, commonEnglishTranslation, Grand Duchess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonEnglishTranslation Context triple: [Velikaya knyazhna, commonEnglishTranslation, Grand Duchess]
-
A.
EnglishTranslation
chosen
Indicates that one expression is the English-language translation equivalent of another expression.
-
B.
translatedIn
Indicates that a work, text, or content has been rendered from its original language into another specified language or linguistic form.
-
C.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
-
D.
EnglishTranslatorOfWork
Indicates that one entity is the person who translated a specific work into English.
-
E.
equivalentEnglishForm
Indicates that two expressions share the same meaning in English, serving as equivalent linguistic forms.
- 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: May 1, 2026, 1:50 a.m.