Triple
T30891072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamburg, Holy Roman Empire |
E786897
|
entity |
| Predicate | timeInEmpire |
P12795
|
FINISHED |
| Object | Middle Ages |
—
|
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: Middle Ages | Statement: [Hamburg, Holy Roman Empire, timeInEmpire, Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInEmpire Context triple: [Hamburg, Holy Roman Empire, timeInEmpire, Middle Ages]
-
A.
timeExistence
chosen
Indicates the period or duration during which an entity exists or is valid.
-
B.
timeAsFlagship
Indicates the period during which an entity served as the primary or leading flagship within a fleet or organization.
-
C.
timeInMyth
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
-
D.
dimensionOfTime
Indicates a temporal measurement or extent that specifies how long something lasts or when it occurs.
-
E.
timeInUniverseEnds
Indicates that the duration or existence of the universe comes to a final end at a specified time or event.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:49 p.m.