Triple
T28563880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egypt under Ramesses II |
E722619
|
entity |
| Predicate | monumentalSite |
P18735
|
FINISHED |
| Object | Ramesseum |
—
|
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: Ramesseum | Statement: [Egypt under Ramesses II, monumentalSite, Ramesseum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monumentalSite Context triple: [Egypt under Ramesses II, monumentalSite, Ramesseum]
-
A.
cultSite
Indicates a location that is or was used for religious or ritual worship activities.
-
B.
notableArchaeologicalSite
chosen
Indicates that a place is recognized as an archaeologically significant site, typically due to important historical remains, artifacts, or research findings.
-
C.
culturalSite
Indicates that one entity is recognized or designated as a cultural site associated with or located in relation to another entity.
-
D.
builtMonument
Indicates that one entity constructed or created a monument in honor of, or related to, another entity.
-
E.
hasArchaeologicalSiteIn
Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
- 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6508dc9408190b7097c846739492c |
completed | May 2, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 4:06 a.m.