Triple
T13487352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sina |
E318539
|
entity |
| Predicate | variantOrDiminutiveOf |
P15846
|
FINISHED |
| Object | names beginning with "Si-" in Germanic languages |
—
|
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: names beginning with "Si-" in Germanic languages | Statement: [Sina, variantOrDiminutiveOf, names beginning with "Si-" in Germanic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: variantOrDiminutiveOf Context triple: [Sina, variantOrDiminutiveOf, names beginning with "Si-" in Germanic languages]
-
A.
hasDiminutive
Indicates that one entity is a diminutive form or smaller/affectionate variant of another entity.
-
B.
nounFormOf
Indicates that one term is the noun form derived from, or corresponding to, another term (typically a verb or adjective).
-
C.
domesticatedForm
Indicates that one entity is the domesticated variant or descendant of another, typically wild, entity.
-
D.
adoptiveNomen
Indicates a naming relationship where one entity has taken on or been given the name of another in an adoptive or non-biological sense.
-
E.
isGivenNameFormOf
chosen
Indicates that one name is a given-name variant or form derived from another name.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3b9b488190bb4e11424ff599c8 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.