Triple
T285809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constantine the Great |
E5881
|
entity |
| Predicate | victoryResult |
P374
|
FINISHED |
| Object | sole ruler of the Roman Empire |
—
|
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: sole ruler of the Roman Empire | Statement: [Constantine the Great, victoryResult, sole ruler of the Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victoryResult Context triple: [Constantine the Great, victoryResult, sole ruler of the Roman Empire]
-
A.
victoryIn
Indicates that one entity achieves a win or success in a specific contest, event, or competitive context involving another entity.
-
B.
typeOfVictory
Indicates the specific manner or category in which a victory was achieved.
-
C.
result
chosen
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
D.
mainWinner
Indicates that one entity is the primary or overall winner in a competition, contest, or comparative outcome relative to others.
-
E.
winningTeam
Indicates which team is the victor in a given competition, game, or contest.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a2605b372c8190831570aa6532cc96 |
completed | Feb. 28, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69a25b7a8d148190aacdcc8ccb35c7f3 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.