Triple
T25019918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | village of Soleb |
E626542
|
entity |
| Predicate | nearbyAncientMonumentType |
P55205
|
FINISHED |
| Object | Egyptian temple |
—
|
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: Egyptian temple | Statement: [village of Soleb, nearbyAncientMonumentType, Egyptian temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyAncientMonumentType Context triple: [village of Soleb, nearbyAncientMonumentType, Egyptian temple]
-
A.
heritageSiteTypeNearby
chosen
Indicates that a particular type of heritage site is located in close proximity to the referenced entity.
-
B.
nearbyRoyalSite
Indicates that one place or object is located close to a site associated with royalty, such as a palace, castle, or royal residence.
-
C.
nearbyMonumentDedication
Indicates that a monument located close to a given reference point has been formally dedicated, typically in honor of a person, event, or concept.
-
D.
monumentType
Indicates the specific kind or category of monument that an entity is classified as.
-
E.
heritageAttraction
Indicates that something is recognized or designated as a heritage-related attraction, typically of cultural, historical, or natural significance.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 18, 2026, 6:06 a.m.