Triple
T25100853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maqbarat Shuhada Uhud |
E628716
|
entity |
| Predicate | approximateNumberOfBurials |
P148531
|
FINISHED |
| Object | around 70 martyrs |
—
|
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: around 70 martyrs | Statement: [Maqbarat Shuhada Uhud, approximateNumberOfBurials, around 70 martyrs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateNumberOfBurials Context triple: [Maqbarat Shuhada Uhud, approximateNumberOfBurials, around 70 martyrs]
-
A.
numberOfBurials
Indicates the total count of burial events associated with a given entity.
-
B.
numberOfGravesApproximate
chosen
Indicates that the stated count of graves is an estimated or approximate number rather than an exact figure.
-
C.
numberOfInterred
Indicates the total count of individuals who are buried or interred at a given site or within a specified context.
-
D.
hasNotableBurials
Indicates that a place, typically a cemetery or burial site, contains the graves or remains of individuals considered notable or significant.
-
E.
cemeteryBurialsSince
Indicates the number of burials that have occurred in a cemetery from a specified point in time onward.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 18, 2026, 6:25 a.m.