Triple
T19468993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pallas’ sword-belt |
E487071
|
entity |
| Predicate | takenAfterEvent |
P3117
|
FINISHED |
| Object | killing of Pallas by Turnus |
—
|
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: killing of Pallas by Turnus | Statement: [Pallas’ sword-belt, takenAfterEvent, killing of Pallas by Turnus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takenAfterEvent Context triple: [Pallas’ sword-belt, takenAfterEvent, killing of Pallas by Turnus]
-
A.
usedAfterEventFor
Indicates that one entity is used only after a specified event has occurred or been completed.
-
B.
tookPlaceAfter
Indicates that one event or occurrence happened later in time than another event or occurrence.
-
C.
createdAfterEvent
chosen
Indicates that the creation of one entity occurred after a specified event in time.
-
D.
succeededByEvent
Indicates that one event directly follows and replaces another in a temporal or sequential order.
-
E.
suppressedAfterEvent
Indicates that something is intentionally hidden, blocked, or prevented from occurring after a specified event has taken place.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633e6fd988190b79be580b65746fe |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.