Triple
T30819002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hizam of the Kiswah |
E784863
|
entity |
| Predicate | isReplacedWith |
P29646
|
FINISHED |
| Object | new Hizam during annual Kiswah replacement |
—
|
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: new Hizam during annual Kiswah replacement | Statement: [Hizam of the Kiswah, isReplacedWith, new Hizam during annual Kiswah replacement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReplacedWith Context triple: [Hizam of the Kiswah, isReplacedWith, new Hizam during annual Kiswah replacement]
-
A.
replacedWith
chosen
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
B.
hasReplaced
Indicates that one entity has taken the place or function of another entity, superseding it in a given context.
-
C.
mayBeReplacedBy
Indicates that one entity can potentially be substituted or superseded by another entity.
-
D.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
E.
seeksToReplace
Indicates an intention or effort by one entity to take over the role, function, or position currently held by 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6906b8f048190b3051f9ece75bd3a |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:44 p.m.