Triple
T35770977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Abbas Shrine |
E1034160
|
entity |
| Predicate | zarihCovers |
P176946
|
FINISHED |
| Object | tomb of Abbas ibn Ali |
—
|
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: tomb of Abbas ibn Ali | Statement: [al-Abbas Shrine, zarihCovers, tomb of Abbas ibn Ali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zarihCovers Context triple: [al-Abbas Shrine, zarihCovers, tomb of Abbas ibn Ali]
-
A.
eraCovered
Indicates that one entity temporally encompasses, includes, or spans the historical period or era associated with another entity.
-
B.
brandCovered
Indicates that one entity provides coverage, representation, or inclusion for a particular brand within its scope (e.g., in a policy, service, catalog, or offering).
-
C.
isCover
chosen
Indicates that one entity functions as a protective or concealing layer over another entity.
-
D.
alsoCovers
Indicates that something extends its scope or applicability to include an additional subject, area, or case beyond what was originally covered.
-
E.
coverUpBy
Indicates that one entity conceals, suppresses, or hides the actions, information, or wrongdoing associated with another entity.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a1f712ec8190a80c885dc84c44ab |
completed | May 3, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.