Triple
T2480639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichskammergericht |
E55805
|
entity |
| Predicate | locationPeriodSpeyer |
P7934
|
FINISHED |
| Object | 1527–1689 |
—
|
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: 1527–1689 | Statement: [Reichskammergericht, locationPeriodSpeyer, 1527–1689]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationPeriodSpeyer Context triple: [Reichskammergericht, locationPeriodSpeyer, 1527–1689]
-
A.
locationPeriod
chosen
Indicates that an entity is associated with being at a particular location during a specified time period.
-
B.
exhibitsPeriod
Indicates that an entity displays, manifests, or shows a particular period or phase as a characteristic or behavior.
-
C.
historicalPartitionPeriod
Indicates that an entity existed, occurred, or is relevant during a specific historical period of territorial partition.
-
D.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
E.
timePeriodOrigin
Indicates that one entity is the time period in which the other entity originated or first came into existence.
- 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd1eb3be481908fa7c6b8f1c78209 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b5e3d481909a5cbc4a96edd24f |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.