Triple
T33233158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hispania |
E850752
|
entity |
| Predicate | romanConquestBegan |
P126247
|
FINISHED |
| Object | 218 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: 218 BC | Statement: [Hispania, romanConquestBegan, 218 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanConquestBegan Context triple: [Hispania, romanConquestBegan, 218 BC]
-
A.
eraOfRomanConquest
Indicates the historical period during which the Roman Empire conquered or brought the referenced entity under Roman control.
-
B.
approximateRomanConquestCentury
chosen
Indicates the approximate century in which the Romans conquered or gained control over a given entity.
-
C.
statusAfterRomanConquest
Indicates the condition or standing of an entity following its conquest by the Roman state or Roman forces.
-
D.
RomanVictory
Indicates that the Romans achieved a successful military outcome over their opponents.
-
E.
firstDacianWar
Indicates the relationship in which an event or context is part of, refers to, or occurs during the First Dacian War.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: May 1, 2026, 1:31 a.m.