Triple
T10723632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Userkaf |
E252882
|
entity |
| Predicate | typeOfMonumentAssociated |
P25584
|
FINISHED |
| Object | pyramids |
—
|
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: pyramids | Statement: [House of Userkaf, typeOfMonumentAssociated, pyramids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMonumentAssociated Context triple: [House of Userkaf, typeOfMonumentAssociated, pyramids]
-
A.
monumentType
chosen
Indicates the specific kind or category of monument that an entity is classified as.
-
B.
monumentSubject
Indicates that the subject serves as the monument or commemorative structure associated with another entity.
-
C.
monumentGroup
Indicates that one monument belongs to, or is categorized within, a specific group or collection of monuments.
-
D.
heritageSiteAssociatedWith
Indicates a relationship where a heritage site is connected or linked to another entity, such as a person, event, culture, or location, through historical, cultural, or symbolic association.
-
E.
builtMonument
Indicates that one entity constructed or created a monument in honor of, or related to, 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d70d46234081908e147638d0cb7e22 |
completed | April 9, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:14 p.m.