Triple
T7201094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Hagen |
E168743
|
entity |
| Predicate | isHistoricalEntity |
P4238
|
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: [Bishopric of Hagen, isHistoricalEntity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricalEntity Context triple: [Bishopric of Hagen, isHistoricalEntity, true]
-
A.
hasHistoricalEntity
Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical context.
-
B.
isHistoric
chosen
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
C.
historicalStatusOf
Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
-
D.
historicalType
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
-
E.
hasHistoricalCategory
Indicates that something is associated with a particular historical classification, period, or type based on its past context or significance.
- 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e94971508190bb38184c9af2fe51 |
completed | March 27, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:52 p.m.