Triple
T29981917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortress of Sargon |
E761617
|
entity |
| Predicate | writtenInCuneiform |
P95800
|
FINISHED |
| Object | Akkadian inscriptions |
—
|
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: Akkadian inscriptions | Statement: [Fortress of Sargon, writtenInCuneiform, Akkadian inscriptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenInCuneiform Context triple: [Fortress of Sargon, writtenInCuneiform, Akkadian inscriptions]
-
A.
oneOfTheEarliestWritingSystemsOf
Indicates that the subject is among the earliest known writing systems associated with the object.
-
B.
usedHieroglyphicWriting
Indicates that the subject employed hieroglyphic writing as a system of written communication.
-
C.
isWrittenWith
chosen
Indicates that something is created or expressed using a particular writing tool, medium, or system.
-
D.
EgyptianVersionInscribedOn
Indicates that an Egyptian-language version of a text or inscription is carved or written onto a particular physical object or surface.
-
E.
hasWritingTraditionSince
Indicates that a writing tradition has been present or established for an entity starting from a specified point in time.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f678da44d48190a14d66b106b7bf88 |
completed | May 2, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:35 p.m.