Triple
T15543134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petrenko |
E370531
|
entity |
| Predicate | hasOriginFromGivenName |
P3325
|
FINISHED |
| Object | Christian name Petro |
—
|
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: Christian name Petro | Statement: [Petrenko, hasOriginFromGivenName, Christian name Petro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginFromGivenName Context triple: [Petrenko, hasOriginFromGivenName, Christian name Petro]
-
A.
hasNameOrigin
chosen
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
B.
hasNameOriginType
Indicates that there is a specific type or category describing the origin of an entity’s name.
-
C.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
D.
hasOriginalNameOf
Indicates that one entity is the original or earlier name from which another entity’s current or later name is derived.
-
E.
isOriginalFamilyNameOf
Indicates that a given family name is the original or birth surname of a person, from which any later or changed surnames may have derived.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04432c3808190bb5b653bf8de30c6 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:07 a.m.