Triple
T25019917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | village of Soleb |
E626542
|
entity |
| Predicate | nearbyAncientCulture |
P126418
|
FINISHED |
| Object | Ancient Egypt |
—
|
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: Ancient Egypt | Statement: [village of Soleb, nearbyAncientCulture, Ancient Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyAncientCulture Context triple: [village of Soleb, nearbyAncientCulture, Ancient Egypt]
-
A.
nearbyArchaeologicalCulture
Indicates that one archaeological culture is geographically close to another archaeological culture.
-
B.
hasNearbyAncientCulture
chosen
Indicates that one entity is geographically close to another entity associated with an ancient culture or civilization.
-
C.
nearAncientRegion
Indicates that one entity is located close to, or in the immediate vicinity of, a specified ancient geographical region.
-
D.
ancientCity
Indicates that the subject is a historically old or long-established city, typically originating from ancient times.
-
E.
archaeologicalRegions
Indicates a relationship where specific areas are designated or recognized as regions of archaeological interest, activity, or 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_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 18, 2026, 6:06 a.m.