Triple
T5672652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giza core limestone |
E125012
|
entity |
| Predicate | associatedMonumentType |
P25584
|
FINISHED |
| Object | royal 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: royal pyramids | Statement: [Giza core limestone, associatedMonumentType, royal pyramids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMonumentType Context triple: [Giza core limestone, associatedMonumentType, royal 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.
otherMonuments
Indicates that there exists a relationship between an entity and additional monuments that are associated with or related to it in some relevant way.
-
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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.