Triple
T9283716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weimar Triangle region (cultural) |
E223132
|
entity |
| Predicate | historicallyRich |
P87384
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Weimar Triangle region (cultural), historicallyRich, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyRich Context triple: [Weimar Triangle region (cultural), historicallyRich, true]
-
A.
historicalInterest
Indicates that one entity has a notable relevance, appeal, or significance to the study or understanding of the past.
-
B.
historicalFocus
Indicates that something is primarily concerned with, centered on, or devoted to a particular historical period, event, or theme.
-
C.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
D.
historicalCategory
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
-
E.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
- F. None of above. chosen
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_69ca842123588190b3f2e1a69037d141 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd081e72988190917f425e64631837 |
completed | April 1, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:34 p.m.