Triple
T32108252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giza Solar Boat Museum |
E820043
|
entity |
| Predicate | primaryExhibitFromDynasty |
P204192
|
FINISHED |
| Object | Fourth Dynasty of Egypt |
E24033
|
NE 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: Fourth Dynasty of Egypt | Statement: [Giza Solar Boat Museum, primaryExhibitFromDynasty, Fourth Dynasty of Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryExhibitFromDynasty Context triple: [Giza Solar Boat Museum, primaryExhibitFromDynasty, Fourth Dynasty of Egypt]
-
A.
depictsDynasty
Indicates that one entity visually represents or portrays a particular dynasty.
-
B.
prominentDynasty
Indicates that a dynasty holds significant historical, political, or cultural importance relative to other dynasties.
-
C.
nativeDynasty
Indicates that a dynasty is indigenous to, or originally from, the place or polity it rules or is associated with.
-
D.
typicallyFromDynasty
chosen
Indicates that an entity is most commonly associated with or originates from a particular dynasty.
-
E.
existedUnderDynasty
Indicates that an entity existed or was in effect during the period of a specified dynasty’s rule.
- F. None of above.
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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2ede030f0c8190a2a5630075998088 |
completed | June 14, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:27 a.m.