Triple
T10062138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mykerinos |
E213015
|
entity |
| Predicate | isAssociatedWithMonumentType |
P25584
|
FINISHED |
| Object | pyramid |
—
|
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: pyramid | Statement: [Mykerinos, isAssociatedWithMonumentType, pyramid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAssociatedWithMonumentType Context triple: [Mykerinos, isAssociatedWithMonumentType, pyramid]
-
A.
monumentType
chosen
Indicates the specific kind or category of monument that an entity is classified as.
-
B.
isMonumentClassic
Indicates that a monument exemplifies classic or traditional architectural or historical style.
-
C.
monumentGroup
Indicates that one monument belongs to, or is categorized within, a specific group or collection of monuments.
-
D.
monumentSubject
Indicates that the subject serves as the monument or commemorative structure associated with another entity.
-
E.
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.
- 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcfd3c6bc8190a21ed3566f9c08d1 |
completed | April 2, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:58 p.m.