Triple
T185414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belshazzar’s Feast |
E3968
|
entity |
| Predicate | portraysEvent |
P6686
|
FINISHED |
| Object | announcement of impending fall of Babylon |
—
|
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: announcement of impending fall of Babylon | Statement: [Belshazzar’s Feast, portraysEvent, announcement of impending fall of Babylon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysEvent Context triple: [Belshazzar’s Feast, portraysEvent, announcement of impending fall of Babylon]
-
A.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
B.
eventRole
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
C.
partOfSeriesOfEvents
Indicates that an event is one element within a larger, ordered sequence of related events.
-
D.
participatedInEvent
Indicates that an entity took part in or was actively involved in a specific event.
-
E.
eveCelebrationOn
Indicates that an event or entity is engaged in or associated with a celebration occurring on a specific date or occasion.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2592867108190b5d316c055575449 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566fb08c81908faff2fde552105d |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a257e763d081908c54ad57d8d3060d |
completed | Feb. 28, 2026, 2:50 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.