Triple
T33353642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raetia |
E854010
|
entity |
| Predicate | conquestCompletedUnder |
P164235
|
FINISHED |
| Object | Augustus |
—
|
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: Augustus | Statement: [Raetia, conquestCompletedUnder, Augustus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conquestCompletedUnder Context triple: [Raetia, conquestCompletedUnder, Augustus]
-
A.
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.
-
B.
conqueredIn
Indicates that one entity gained control over another entity or territory as a result of a specific conquest event or campaign.
-
C.
realmConqueredBy
chosen
Indicates that a particular realm or territory has been taken over and brought under the control of a specified conqueror.
-
D.
hasConquered
Indicates that one entity has taken control over another entity or its territory through force or domination.
-
E.
conqueredInPartBy
Indicates that one entity has gained control over a portion, but not the entirety, of another entity through conquest.
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.