Triple
T32230817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebhepetre |
E823335
|
entity |
| Predicate | appearsOnMonumentsOf |
P85290
|
FINISHED |
| Object | Mentuhotep II |
—
|
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: Mentuhotep II | Statement: [Nebhepetre, appearsOnMonumentsOf, Mentuhotep II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsOnMonumentsOf Context triple: [Nebhepetre, appearsOnMonumentsOf, Mentuhotep II]
-
A.
usedInMonument
Indicates that something serves as a material, component, or element incorporated into the construction or design of a monument.
-
B.
monumentDepicts
chosen
Indicates that a monument visually represents, portrays, or is dedicated to a particular person, event, concept, or object.
-
C.
appliesToMonument
Indicates that something (such as a rule, status, or attribute) is relevant or applicable specifically to a monument.
-
D.
knownMonuments
Indicates that an entity is recognized or identified as a monument by another entity or within a given context.
-
E.
monumentSubject
Indicates that the subject serves as the monument or commemorative structure associated with 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 1, 2026, 12:39 a.m.