Triple
T9702995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viktorovich |
E234823
|
entity |
| Predicate | namingConventionRole |
P55932
|
FINISHED |
| Object | indicates father’s given 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: indicates father’s given name | Statement: [Viktorovich, namingConventionRole, indicates father’s given name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingConventionRole Context triple: [Viktorovich, namingConventionRole, indicates father’s given name]
-
A.
namingConventionType
Indicates the specific style or set of rules used for naming entities or elements in a given context.
-
B.
namingStructure
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
-
C.
nicknameForRole
Indicates that one entity is an informal or alternative name commonly used to refer to a particular role or position represented by another entity.
-
D.
notationRole
Indicates a role or function that an entity plays specifically within a system of notation or symbolic representation.
-
E.
roleInNomenclature
chosen
Indicates the specific function or status an entity holds within a particular naming or classification system.
- 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d73a0148190ad4178fd462cdd9c |
completed | April 1, 2026, 10:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03b641408190942464eaf174c6b5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:18 p.m.