Triple
T31321977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahmad ibn Muhammad al-Hasib |
E798770
|
entity |
| Predicate | al-HasibMeans |
P171243
|
FINISHED |
| Object | the calculator |
—
|
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: the calculator | Statement: [Ahmad ibn Muhammad al-Hasib, al-HasibMeans, the calculator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: al-HasibMeans Context triple: [Ahmad ibn Muhammad al-Hasib, al-HasibMeans, the calculator]
-
A.
همسر
Indicates a marital relationship where one person is the spouse of another.
-
B.
المالك
Indicates a relationship where one entity is the owner or possessor of another entity.
-
C.
النسب
Indicates a genealogical or familial relationship linking one entity to another through lineage or descent.
-
D.
hizb
Indicates a relationship in which an entity is affiliated with, belongs to, or is associated with a political party or organized group.
-
E.
associatedCaliph
Indicates a relationship where an entity is linked or connected to a specific caliph, typically through rule, patronage, affiliation, or historical association.
- F. None of above. chosen
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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f11ba548190b8ad25fafb07b62b |
completed | May 3, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69ea761848190acb31298e65b7892 |
completed | May 3, 2026, 1:02 a.m. |
Created at: April 29, 2026, 9:15 p.m.