Triple
T27369934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vordingborg |
E690284
|
entity |
| Predicate | hasHistoricEventType |
P186444
|
FINISHED |
| Object | medieval royal residence |
—
|
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: medieval royal residence | Statement: [Vordingborg, hasHistoricEventType, medieval royal residence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricEventType Context triple: [Vordingborg, hasHistoricEventType, medieval royal residence]
-
A.
hasHistoricType
Indicates that an entity is associated with a specific historical classification, category, or type it held in the past.
-
B.
hasHistoricResourceType
Indicates that an entity is associated with a particular category or type of historic resource.
-
C.
hasHistoricProperty
Indicates that one entity possesses, contains, or is associated with a property that has historical significance or heritage value.
-
D.
hasHistoricalProcess
Indicates that an entity is associated with, or characterized by, a historical process or sequence of events that unfolded over time.
-
E.
hasHistoricMP
Indicates that an entity is or has been represented by a specific Member of Parliament at some point in the past.
- 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_69ef51ff826081909e42c8e2bfb97941 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: April 27, 2026, 12:18 p.m.