Triple
T10321462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Year of the Sword |
E242146
|
entity |
| Predicate | hasMemoryIn |
P93366
|
FINISHED |
| Object | Assyrian collective memory |
—
|
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: Assyrian collective memory | Statement: [Year of the Sword, hasMemoryIn, Assyrian collective memory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemoryIn Context triple: [Year of the Sword, hasMemoryIn, Assyrian collective memory]
-
A.
builtInMemoryOf
Indicates that something was constructed as a tribute or commemoration to a particular person, group, or event.
-
B.
hasUserMemory
Indicates that an entity maintains or is associated with stored information about a specific user.
-
C.
hasRAM
Indicates that an entity possesses or is equipped with a specified amount or type of random-access memory (RAM).
-
D.
hasMemorySlot
Indicates that an entity possesses a specific memory slot or storage location for holding information or data.
-
E.
hasStorage
Indicates that one entity provides or contains storage capacity or space for another entity or resource.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d7cada7881908beba55a1dc9ecb9 |
completed | April 7, 2026, 10:09 a.m. |
Created at: April 6, 2026, 11:50 a.m.