Triple
T31747232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tomb of Psusennes I |
E810303
|
entity |
| Predicate | currentLocationOfMainTreasures |
P36131
|
FINISHED |
| Object | Egyptian Museum in Cairo |
—
|
NE NERFINISHED |
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: Egyptian Museum in Cairo | Statement: [tomb of Psusennes I, currentLocationOfMainTreasures, Egyptian Museum in Cairo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentLocationOfMainTreasures Context triple: [tomb of Psusennes I, currentLocationOfMainTreasures, Egyptian Museum in Cairo]
-
A.
relicsLocatedIn
chosen
Indicates that certain relics are situated, stored, or found within a specific location.
-
B.
treasureOwnedBy
Indicates that a particular treasure is possessed or legally held by a specific owner.
-
C.
loreLocation
Indicates that something is the place or setting where related background story, history, or world-building information is situated or associated.
-
D.
treasureInvolved
Indicates that a situation, event, or action involves or is related to treasure in some significant way.
-
E.
majorShrineLocation
Indicates that a major religious shrine is located at or associated with a particular place or geographic location.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: April 30, 2026, 11:27 p.m.