Triple
T19431977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maksimovna |
E486135
|
entity |
| Predicate | positionInNameOrder |
P1082
|
FINISHED |
| Object | second name element in Russian full name |
—
|
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: second name element in Russian full name | Statement: [Maksimovna, positionInNameOrder, second name element in Russian full name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInNameOrder Context triple: [Maksimovna, positionInNameOrder, second name element in Russian full name]
-
A.
namePosition
chosen
Indicates the positional or ordering relationship of a name within a sequence or structured context (e.g., first, last, or specific index).
-
B.
hasNameOrder
Indicates the specific sequence or arrangement in which the components of a name (e.g., given name, family name, titles) are ordered.
-
C.
namedAfterPosition
Indicates that an entity is named after a specific position, role, or rank associated with it.
-
D.
positionInFamilyBirthOrder
Indicates the relative order in which a person was born within their family (e.g., first-born, middle child, last-born).
-
E.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6335b4e388190913ded15ad165b7b |
completed | April 20, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.