Triple
T5901778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bab al-Kalabsha |
E131242
|
entity |
| Predicate | usedToContain |
P46132
|
FINISHED |
| Object | original location of Temple of Kalabsha |
—
|
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: original location of Temple of Kalabsha | Statement: [Bab al-Kalabsha, usedToContain, original location of Temple of Kalabsha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToContain Context triple: [Bab al-Kalabsha, usedToContain, original location of Temple of Kalabsha]
-
A.
containedWith
chosen
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
-
B.
usedToBeCalled
Indicates that an entity previously had a different name or title than the one it currently has.
-
C.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
-
D.
usedToBe
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
-
E.
usedToSearchFor
Indicates that one entity serves as a tool, method, or resource employed to look for, locate, or retrieve 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0334dc8248190b7394dcece362d52 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.