Triple
T36180556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Renty |
E1046695
|
entity |
| Predicate | emperorAtTime |
P10335
|
FINISHED |
| Object | Charles V |
—
|
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: Charles V | Statement: [Battle of Renty, emperorAtTime, Charles V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emperorAtTime Context triple: [Battle of Renty, emperorAtTime, Charles V]
-
A.
eraOfEmperor
Indicates the historical time period during which a particular emperor held power or reigned.
-
B.
hasEmperor
chosen
Indicates that an entity is ruled or governed by an emperor.
-
C.
rulingEmperorPersonalName
Indicates that the specified personal name belongs to the individual who is (or was) serving as the ruling emperor.
-
D.
wasEmperorDuring
Indicates that a person held the position of emperor during a specified time period or historical era.
-
E.
wasEmperorOf
Indicates that one entity held the position and authority of emperor over another entity (typically a state, empire, or territory).
- 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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.