Triple
T36788679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mālik ibn Wahib |
E908991
|
entity |
| Predicate | relativeNameVariant |
P161294
|
FINISHED |
| Object | Wahib |
E1655957
|
NE 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: Wahib | Statement: [Mālik ibn Wahib, relativeNameVariant, Wahib]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeNameVariant Context triple: [Mālik ibn Wahib, relativeNameVariant, Wahib]
-
A.
relativeAlias
Indicates that one entity is known or referred to by an alternative name or label that is contextually related to another entity.
-
B.
nameHasVariant
chosen
Indicates that an entity’s name has an alternative or variant form.
-
C.
exportVariantName
Indicates that one entity is the name or label of a specific variant of another entity intended for export.
-
D.
hasOfficialNameVariant
Indicates that an entity has an alternative official form or version of its name.
-
E.
dstVariantName
Indicates that an entity has a specific variant name used or assigned as the destination in a mapping, transformation, or versioning context.
- F. None of above.
Provenance (4 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3d17a5b8448190b3518c2f0054bb67 |
completed | June 25, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.