Triple
T26685694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hovedøya Abbey |
E672736
|
entity |
| Predicate | functionDuringMiddleAges |
P166160
|
FINISHED |
| Object | religious center |
—
|
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: religious center | Statement: [Hovedøya Abbey, functionDuringMiddleAges, religious center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionDuringMiddleAges Context triple: [Hovedøya Abbey, functionDuringMiddleAges, religious center]
-
A.
isMedieval
Indicates that something belongs to, originates from, or is characteristic of the medieval (Middle Ages) period.
-
B.
medievalStatus
Indicates the social, legal, or hierarchical standing an entity holds within a medieval societal structure.
-
C.
medievalState
Indicates that an entity functioned as a state or political unit during the medieval historical period.
-
D.
medievalAssociation
Indicates a relationship or involvement between entities specifically within a medieval context, such as shared roles, activities, or affiliations characteristic of the Middle Ages.
-
E.
medievalSignificance
Indicates that something holds notable importance, influence, or relevance within the context of the medieval period.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 27, 2026, 3:22 a.m.