Triple
T8266052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Kadesh |
E193303
|
entity |
| Predicate | EgyptianVersionInscribedOn |
P81590
|
FINISHED |
| Object | temple walls at Karnak |
—
|
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: temple walls at Karnak | Statement: [Treaty of Kadesh, EgyptianVersionInscribedOn, temple walls at Karnak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EgyptianVersionInscribedOn Context triple: [Treaty of Kadesh, EgyptianVersionInscribedOn, temple walls at Karnak]
-
A.
pyramidTextInscriptions
Indicates that the subject has text inscriptions located on or within a pyramid.
-
B.
nameInHieroglyphs
Indicates that an entity’s name is written or represented using hieroglyphic script.
-
C.
broughtToEgypt
Indicates that one entity caused another entity to be taken or transported to Egypt.
-
D.
usedRoyalSerekh
Indicates that one entity employed or displayed the royal serekh (a pharaonic name emblem) associated with another entity.
-
E.
associatedWithPharaoh
Indicates a relationship in which an entity has a connection, link, or involvement with a pharaoh, such as through service, rule, influence, or historical association.
- F. None of above. chosen
Provenance (4 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb794c54448190a685b8d0070980d7 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4ab5162c8190bddd696078689895 |
completed | March 31, 2026, 4:16 a.m. |
Created at: March 30, 2026, 5:50 p.m.