Triple
T12226355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princes' War |
E291359
|
entity |
| Predicate | timeWithinEntity |
P6261
|
FINISHED |
| Object | reign of Charles V as Holy Roman Emperor |
—
|
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: reign of Charles V as Holy Roman Emperor | Statement: [Princes' War, timeWithinEntity, reign of Charles V as Holy Roman Emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeWithinEntity Context triple: [Princes' War, timeWithinEntity, reign of Charles V as Holy Roman Emperor]
-
A.
timePeriodWithin
chosen
Indicates that one time period is entirely contained within the bounds of another time period.
-
B.
timeDomain
Indicates that something is characterized, defined, or analyzed with respect to time rather than another domain (such as frequency or space).
-
C.
timeBehind
Indicates that one entity occurs or is positioned later in time than another, lagging behind it on a temporal scale.
-
D.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
E.
timeProperty
Indicates that one entity specifies, constrains, or characterizes a temporal aspect or timing-related attribute of 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d924a3973c8190a882046963b320fb |
completed | April 10, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69d91c41bcbc81909782f4e3c571b218 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.