Triple
T17266714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falerii Veteres |
E419145
|
entity |
| Predicate | timeOfRomanConquest |
P88235
|
FINISHED |
| Object | 4th 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: 4th century BC | Statement: [Falerii Veteres, timeOfRomanConquest, 4th century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfRomanConquest Context triple: [Falerii Veteres, timeOfRomanConquest, 4th century BC]
-
A.
eraOfRomanConquest
chosen
Indicates the historical period during which the Roman Empire conquered or brought the referenced entity under Roman control.
-
B.
RomanVictory
Indicates that the Romans achieved a successful military outcome over their opponents.
-
C.
yearOfSackOfRome
Indicates the specific year in which the Sack of Rome took place.
-
D.
romanRuleEnded
Indicates that a period of Roman political or administrative control over a place or people has come to an end.
-
E.
yearInRomanHistory
Indicates that a specific year is notable or relevant within the context of Roman history.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f45bf608190bcb48783d0d6fb85 |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.