Triple
T18116887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legio IX Hispana |
E433626
|
entity |
| Predicate | lastCertainRecordDate |
P21092
|
FINISHED |
| Object | early 2nd century CE |
—
|
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: early 2nd century CE | Statement: [Legio IX Hispana, lastCertainRecordDate, early 2nd century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastCertainRecordDate Context triple: [Legio IX Hispana, lastCertainRecordDate, early 2nd century CE]
-
A.
lastEntryDate
chosen
Indicates the date on which the most recent entry, record, or update associated with the subject occurred.
-
B.
latestPossibleDate
Indicates the most recent date on which a given event, condition, or state can validly or feasibly occur.
-
C.
lastRecordedEvent
Indicates the most recent event that has been recorded for a given entity or context.
-
D.
lastTestDate
Indicates the date on which the most recent test associated with the entity was conducted.
-
E.
lastSessionDate
Indicates the date on which the most recent session involving the entity took 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd67a2481909d27a4a49b095f8c |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.