Triple
T31870447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tomb of Shoshenq II |
E813582
|
entity |
| Predicate | hasOccupantTitle |
P172676
|
FINISHED |
| Object | pharaoh |
—
|
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: pharaoh | Statement: [tomb of Shoshenq II, hasOccupantTitle, pharaoh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOccupantTitle Context triple: [tomb of Shoshenq II, hasOccupantTitle, pharaoh]
-
A.
hasTitleHolder
Indicates that one entity is the current or designated holder of a specific title, position, or honor associated with another entity.
-
B.
hasTitleHolderResidence
Indicates that a specified residence is the official home or dwelling place of the current holder of a particular title.
-
C.
hasSeatTitle
Indicates that an entity holds a position or seat identified by a specific title.
-
D.
hasTitleOf
Indicates that one entity holds, bears, or is designated by the official title, name, or rank specified by another entity.
-
E.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
- F. None of above. chosen
Provenance (4 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b09bc8bc81909ca5fb69d9628355 |
completed | May 3, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6af7d92008190aead47eaae8cc091 |
completed | May 3, 2026, 2:14 a.m. |
Created at: April 30, 2026, 11:54 p.m.