Triple
T9956782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashurnasirpal II |
E195464
|
entity |
| Predicate | heldEvent |
P22468
|
FINISHED |
| Object | inaugural banquet at Kalhu |
—
|
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: inaugural banquet at Kalhu | Statement: [Ashurnasirpal II, heldEvent, inaugural banquet at Kalhu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldEvent Context triple: [Ashurnasirpal II, heldEvent, inaugural banquet at Kalhu]
-
A.
heldOn
Indicates that an event or activity takes place at a specific time, date, or occasion.
-
B.
areHeldIn
Indicates that events, activities, or objects take place or are located within a particular venue, container, or setting.
-
C.
hadEvent
chosen
Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
-
D.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
-
E.
heldEvery
Indicates that an entity consistently possessed or maintained control of another entity throughout every instance or period within a specified range.
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6976b50819097a0ae347354e92c |
completed | April 2, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:46 p.m.