Triple
T1859466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menkaure |
E41780
|
entity |
| Predicate | artifactsFoundAt |
P19329
|
FINISHED |
| Object | valley temple of Menkaure |
—
|
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: valley temple of Menkaure | Statement: [Menkaure, artifactsFoundAt, valley temple of Menkaure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artifactsFoundAt Context triple: [Menkaure, artifactsFoundAt, valley temple of Menkaure]
-
A.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
B.
inscriptionsFoundAt
Indicates that inscriptions are discovered or located at a particular place or site.
-
C.
locatedAtTimeOfDiscovery
Indicates the place where something was situated at the moment it was first discovered.
-
D.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
E.
archaeologicalFindsInclude
chosen
Indicates that the set of archaeological finds at a site or context contains or encompasses the specified items or types of artifacts.
- 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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb231de14819091da3a20ed03c430 |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafde4598819099d8229128348fd3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.