Triple
T31114464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rayhani |
E793042
|
entity |
| Predicate | notableCalligrapher |
P202119
|
FINISHED |
| Object | Yaqut al-Musta‘simi |
E224935
|
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: Yaqut al-Musta‘simi | Statement: [Rayhani, notableCalligrapher, Yaqut al-Musta‘simi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCalligrapher Context triple: [Rayhani, notableCalligrapher, Yaqut al-Musta‘simi]
-
A.
notableCulturalFigure
Indicates that a person holds significant influence or recognition within a culture’s arts, traditions, values, or public life.
-
B.
notableInscriptionBy
Indicates that an inscription of particular note or significance on an entity was created, authored, or carved by a specified agent.
-
C.
notableMaker
Indicates that one entity is a well-known or significant creator, producer, or manufacturer of the other entity.
-
D.
hasCalligraphicInfluence
chosen
Indicates that one entity has influenced or shaped the calligraphic style, techniques, or aesthetic of another entity.
-
E.
namedForCulturalFigure
Indicates that one entity is named in honor of, or derived from the name of, a notable cultural figure.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2a1e138dec8190a10b9d0d2fdd0fd4 |
completed | June 11, 2026, 2:31 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:04 p.m.