Triple
T28824553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flavia Caesariensis |
E727865
|
entity |
| Predicate | endStatus |
P70625
|
FINISHED |
| Object | province dissolved in early 5th century AD |
—
|
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: province dissolved in early 5th century AD | Statement: [Flavia Caesariensis, endStatus, province dissolved in early 5th century AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endStatus Context triple: [Flavia Caesariensis, endStatus, province dissolved in early 5th century AD]
-
A.
statusEndsWhen
chosen
Indicates that a particular status or condition ceases to hold when a specified event, time, or state occurs.
-
B.
endOfState
Indicates the point or condition at which a particular state, situation, or process comes to an end.
-
C.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
-
D.
endOfSeriesStatus
Indicates that a series, sequence, or collection has reached its final state or completion status.
-
E.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6593772ec8190805b9fabde7083f4 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:35 a.m.