Triple
T13014819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maurice, Elector of Saxony |
E322521
|
entity |
| Predicate | laterAlly |
P61003
|
FINISHED |
| Object | Protestant princes opposed to Charles V |
—
|
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: Protestant princes opposed to Charles V | Statement: [Maurice, Elector of Saxony, laterAlly, Protestant princes opposed to Charles V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAlly Context triple: [Maurice, Elector of Saxony, laterAlly, Protestant princes opposed to Charles V]
-
A.
formerAllyOf
Indicates that an entity was once an ally of another entity but that alliance has since ended.
-
B.
laterAlliesWith
chosen
Indicates that two entities become allies at a later time, after not being allied initially.
-
C.
primaryAlly
Indicates that one entity is the main or most significant ally or supportive partner of another entity.
-
D.
laterEnemyOf
Indicates that one entity becomes an enemy of another at a later time, after not initially being in an antagonistic relationship.
-
E.
sometimesAllyOf
Indicates that one entity is an ally of another in some situations or periods, but not consistently or universally.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ecd04748190ade2530ee5db35fe |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:50 p.m.