Triple
T5630357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fusus al-Hikam |
E147813
|
entity |
| Predicate | circaComposition |
P64676
|
FINISHED |
| Object | c. 1229 CE |
—
|
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: c. 1229 CE | Statement: [Fusus al-Hikam, circaComposition, c. 1229 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circaComposition Context triple: [Fusus al-Hikam, circaComposition, c. 1229 CE]
-
A.
musicComposedIn
Indicates that a piece of music was created or composed in a specific place or location.
-
B.
notableComposition
Indicates that an entity is a significant or well-known work created by another entity, such as a notable musical, literary, or artistic composition.
-
C.
hasMusicalComposer
Indicates that one entity serves as the musical composer responsible for creating the music associated with another entity.
-
D.
musicComposer
Indicates that one entity is the creator or writer of a piece of music associated with another entity.
-
E.
partOfComposerOeuvre
Indicates that a musical work belongs to and is included within the overall body of compositions created by a particular composer.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0223c722481908bc3684825b3977a |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:40 p.m.