Triple
T9960889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Лев |
E195563
|
entity |
| Predicate | языкПроисхождения |
P506
|
FINISHED |
| Object | латинский язык |
—
|
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: латинский язык | Statement: [Лев, языкПроисхождения, латинский язык]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: языкПроисхождения Context triple: [Лев, языкПроисхождения, латинский язык]
-
A.
etymologicalLanguage
chosen
Indicates the language from which a word or term is historically derived in its etymology.
-
B.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another entity.
-
C.
etymologicalLanguageFamily
Indicates that one entity is the language family from which the other entity is etymologically derived or historically originates.
-
D.
historicalOriginMeaning
Indicates that one entity explains the original historical source or derivational meaning of another entity.
-
E.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6d219c48190b2084b0eb07ae125 |
completed | April 2, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:47 p.m.