Triple
T34399086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aulus Postumius Albus |
E882923
|
entity |
| Predicate | traditionalDateOfBattle |
P31438
|
FINISHED |
| Object | early 5th century BC |
—
|
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 5th century BC | Statement: [Aulus Postumius Albus, traditionalDateOfBattle, early 5th century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalDateOfBattle Context triple: [Aulus Postumius Albus, traditionalDateOfBattle, early 5th century BC]
-
A.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
B.
timeOfMajorBattle
Indicates the specific time at which a major battle took place.
-
C.
yearOfBattle
Indicates the specific calendar year in which a particular battle took place.
-
D.
traditionallyDated
chosen
Indicates that something is assigned a date based on traditional or customary chronology rather than on firmly established historical or scientific evidence.
-
E.
dateOfVictory
Indicates the specific calendar date on which a victory or winning outcome occurred.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: May 1, 2026, 1:59 a.m.