Triple
T27169398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takelot III |
E682862
|
entity |
| Predicate | usedHieroglyphicWriting |
P162232
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Takelot III, usedHieroglyphicWriting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedHieroglyphicWriting Context triple: [Takelot III, usedHieroglyphicWriting, true]
-
A.
nameInHieroglyphs
Indicates that an entity’s name is written or represented using hieroglyphic script.
-
B.
hasWritingTraditionSince
Indicates that a writing tradition has been present or established for an entity starting from a specified point in time.
-
C.
EgyptianVersionInscribedOn
Indicates that an Egyptian-language version of a text or inscription is carved or written onto a particular physical object or surface.
-
D.
hasWritingTraditionVia
Indicates that an entity possesses or participates in a writing tradition by means of, or through the mediation of, another specified entity or method.
-
E.
usedRoyalSerekh
Indicates that one entity employed or displayed the royal serekh (a pharaonic name emblem) associated with another entity.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62545e210819090004d7c65f4898d |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f622a8fe7c819096e8a43db263a423 |
completed | May 2, 2026, 4:13 p.m. |
Created at: April 27, 2026, 9:22 a.m.