Triple
T28775455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silures |
E726519
|
entity |
| Predicate | capitalAfterConquest |
P46175
|
FINISHED |
| Object | Venta Silurum |
—
|
NE NERFINISHED |
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: Venta Silurum | Statement: [Silures, capitalAfterConquest, Venta Silurum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalAfterConquest Context triple: [Silures, capitalAfterConquest, Venta Silurum]
-
A.
realmConqueredBy
Indicates that a particular realm or territory has been taken over and brought under the control of a specified conqueror.
-
B.
convertedAfterConquest
Indicates that one entity underwent conversion (typically religious or cultural) as a direct consequence of being conquered by another entity.
-
C.
afterConquest
chosen
Indicates that one event, state, or condition occurs subsequent to and as a result of a conquest having taken place.
-
D.
afterConquestBy
Indicates that one entity exists in a state, condition, or situation that occurs subsequent to and as a result of being conquered by another entity.
-
E.
conqueredIn
Indicates that one entity gained control over another entity or territory as a result of a specific conquest event or campaign.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 28, 2026, 6:17 a.m.