Triple
T26309380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ʿĀm al-Ḥuzn |
E661777
|
entity |
| Predicate | chronologicalPositionInSīra |
P160870
|
FINISHED |
| Object | late Meccan period |
—
|
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: late Meccan period | Statement: [ʿĀm al-Ḥuzn, chronologicalPositionInSīra, late Meccan period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalPositionInSīra Context triple: [ʿĀm al-Ḥuzn, chronologicalPositionInSīra, late Meccan period]
-
A.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
B.
chronologicalPositionInFamilySaga
Indicates the relative order in which an event, episode, or member appears within the timeline of a family saga.
-
C.
chronologicalPositionInEpicCycle
chosen
Indicates the relative order or placement of an event, episode, or work within the overall sequence of an epic cycle.
-
D.
chronologicRank
Indicates the relative position or order of something within a sequence based on time.
-
E.
positionInDynasty
Indicates the specific role or rank an individual holds within a particular dynasty’s internal hierarchy.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 26, 2026, 10:21 p.m.