Triple
T26418857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senedj |
E664175
|
entity |
| Predicate | possibleVariantName |
P104759
|
FINISHED |
| Object | Sened |
—
|
NE NERFINISHED |
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: Sened | Statement: [Senedj, possibleVariantName, Sened]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleVariantName Context triple: [Senedj, possibleVariantName, Sened]
-
A.
exportVariantName
Indicates that one entity is the name or label of a specific variant of another entity intended for export.
-
B.
nameHasVariant
Indicates that an entity’s name has an alternative or variant form.
-
C.
dstVariantName
Indicates that an entity has a specific variant name used or assigned as the destination in a mapping, transformation, or versioning context.
-
D.
likelyVariantOf
chosen
Indicates that one entity is probably a variant, version, or alternative form of another entity, based on available evidence or similarity.
-
E.
hasOfficialNameVariant
Indicates that an entity has an alternative official form or version of its 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 26, 2026, 11:42 p.m.