Triple
T9270223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farewell Sermon of Prophet Muhammad |
E222805
|
entity |
| Predicate | deliveredInYearGregorianApprox |
P49730
|
FINISHED |
| Object | 632 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: 632 CE | Statement: [Farewell Sermon of Prophet Muhammad, deliveredInYearGregorianApprox, 632 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deliveredInYearGregorianApprox Context triple: [Farewell Sermon of Prophet Muhammad, deliveredInYearGregorianApprox, 632 CE]
-
A.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
B.
deliveredAt
Indicates the specific time or location at which something (such as a message, product, or service) is delivered.
-
C.
releaseApproximateYear
chosen
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
-
D.
deliveredDuring
Indicates that one entity was delivered within the time span defined by another entity or temporal interval.
-
E.
derivationYear
Indicates the year in which something was derived, produced, or generated from a source.
- 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd078525308190abfb883123742d3f |
completed | April 1, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:33 p.m.