Triple
T18581291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andreychuk |
E454119
|
entity |
| Predicate | sharesEtymologicalTypeWith |
P28322
|
FINISHED |
| Object | Slavic surnames |
—
|
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: Slavic surnames | Statement: [Andreychuk, sharesEtymologicalTypeWith, Slavic surnames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesEtymologicalTypeWith Context triple: [Andreychuk, sharesEtymologicalTypeWith, Slavic surnames]
-
A.
sharesEtymologyWith
chosen
Indicates that two terms originate from the same linguistic root or source word, or have closely related historical word origins.
-
B.
sharesLinguisticFamilyWith
Indicates that two languages belong to the same linguistic family or branch within a language family.
-
C.
etymologyRelatesTo
Indicates a relationship where one term’s origin, history, or derivation is connected to another linguistic form, word, or source.
-
D.
hasEtymologicalBasis
Indicates that one term, name, or expression is derived from, based on, or historically formed from the other in terms of linguistic origin.
-
E.
sharesSpellingWith
Indicates that two entities have identical or substantially identical written forms (i.e., they are spelled the same way).
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e543cffd34819090d636fd584f51db |
completed | April 19, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.