Triple
T9487655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquileia |
E228801
|
entity |
| Predicate | sackedInYear |
P88398
|
FINISHED |
| Object | 452 |
—
|
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: 452 | Statement: [Aquileia, sackedInYear, 452]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sackedInYear Context triple: [Aquileia, sackedInYear, 452]
-
A.
sackedBy
Indicates that one entity was dismissed or fired from a position or job by another entity.
-
B.
sacked
Indicates that one entity has dismissed or removed another from a position, role, or employment, typically as an authoritative or punitive action.
-
C.
relegatedFromBPoolPreviousYear
Indicates that an entity was demoted or dropped from the B Pool in the previous year.
-
D.
relegatedFrom
Indicates that an entity has been demoted, downgraded, or moved from a higher status, level, or position to a lower one, typically as a result of performance or evaluation.
-
E.
teamEndYear
Indicates the year in which an entity’s association with a particular team ended.
- 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd80c443b88190968d2092a73e1ee4 |
completed | April 1, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69cca561e6b0819090aa795f3c3a2083 |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:55 p.m.