Triple
T2878253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vladimirovich |
E56930
|
entity |
| Predicate | followsElement |
P134
|
FINISHED |
| Object | 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: given name | Statement: [Vladimirovich, followsElement, given name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsElement Context triple: [Vladimirovich, followsElement, given name]
-
A.
followsFrom
Indicates that one fact, event, or state logically or causally results from, is implied by, or comes as a consequence of another.
-
B.
followsUnit
Indicates that one unit comes directly after or is ordered subsequent to another unit in a sequence or structure.
-
C.
follows
chosen
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
D.
followsCharacter
Indicates that one character moves or acts after another character, maintaining a trailing or subsequent position or sequence relative to them.
-
E.
mayBeFollowedBy
Indicates that one event, state, or item is allowed or able to occur immediately after another in a sequence.
- 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe008925c81909683d0ebc6227e5e |
completed | March 7, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69abdd15cbf08190bf7fea5ea516848a |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.