Triple
T14188413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vyacheslav Ivanov |
E351642
|
entity |
| Predicate | typeOfRower |
P113140
|
FINISHED |
| Object | sculler |
—
|
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: sculler | Statement: [Vyacheslav Ivanov, typeOfRower, sculler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRower Context triple: [Vyacheslav Ivanov, typeOfRower, sculler]
-
A.
hasRowingSide
Indicates that an entity involved in rowing is associated with a specific side (e.g., port or starboard) on which it rows.
-
B.
oarsPerRower
Indicates the number of oars assigned to or used by each individual rower in a rowing context.
-
C.
oarType
Indicates the specific kind or category of oar associated with or used in an activity, object, or context.
-
D.
hullType
Indicates the specific structural design or configuration of an object's hull, typically classifying how its outer body or shell is shaped or constructed.
-
E.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
- F. None of above. chosen
Provenance (4 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61de509881908967ef5031f2a8d9 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:03 a.m.