Triple
T33777512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corieltauvi |
E865560
|
entity |
| Predicate | conqueredDuringReignOf |
P149907
|
FINISHED |
| Object | Claudius |
—
|
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: Claudius | Statement: [Corieltauvi, conqueredDuringReignOf, Claudius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conqueredDuringReignOf Context triple: [Corieltauvi, conqueredDuringReignOf, Claudius]
-
A.
conqueredIn
Indicates that one entity gained control over another entity or territory as a result of a specific conquest event or campaign.
-
B.
realmConqueredBy
Indicates that a particular realm or territory has been taken over and brought under the control of a specified conqueror.
-
C.
capturedDuringReignOf
chosen
Indicates that one entity was captured while another entity was in power or ruling (i.e., during the time span of that entity’s reign).
-
D.
conqueredByRuler
Indicates that a place, people, or entity was taken over and brought under control through force or domination by a specific ruler.
-
E.
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.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.