Triple
T25160534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Town Innsbruck |
E626423
|
entity |
| Predicate | historicallyDevelopedInPeriod |
P95
|
FINISHED |
| Object | Middle Ages |
E2729
|
NE 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: Middle Ages | Statement: [Old Town Innsbruck, historicallyDevelopedInPeriod, Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyDevelopedInPeriod Context triple: [Old Town Innsbruck, historicallyDevelopedInPeriod, Middle Ages]
-
A.
wasDevelopedInPeriod
chosen
Indicates that something was created, produced, or brought into existence during a specified time period.
-
B.
historicallyDevelopedWith
Indicates that one entity evolved, emerged, or was formed over time in conjunction with or as a result of the development of another entity.
-
C.
developedFromPeriod
Indicates that something originated, evolved, or was derived from a specified historical or temporal period.
-
D.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
E.
locatedInHistoricPeriod
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
- F. None of above.
Provenance (4 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1067bd00a88190b6c599c6ebc9044e |
completed | May 22, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 18, 2026, 6:31 a.m.