Triple
T28042134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vor Frue Kirke |
E708573
|
entity |
| Predicate | firstChurchOnSiteDate |
P27687
|
FINISHED |
| Object | 12th century |
—
|
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: 12th century | Statement: [Vor Frue Kirke, firstChurchOnSiteDate, 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstChurchOnSiteDate Context triple: [Vor Frue Kirke, firstChurchOnSiteDate, 12th century]
-
A.
firstChapelBuilt
Indicates that the subject is the location or entity where the first chapel was constructed or established.
-
B.
firstStoneChurchBuilt
Indicates that the subject is the first stone church constructed in relation to the specified place or context.
-
C.
originalChurchBuilt
Indicates that a particular church building was initially constructed at a given time or by a specified agent, before any later reconstructions or modifications.
-
D.
earlierChurchOnSite
chosen
Indicates that an earlier church building previously existed on the same site as the referenced church or structure.
-
E.
foundingLocationOfChurch
Indicates the place where a particular church was originally founded or established.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69ffa5f31c8881908c26e2aa52df6ece |
completed | May 9, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69ffa42aee408190ad1a5f285688b338 |
completed | May 9, 2026, 9:16 p.m. |
Created at: April 27, 2026, 8:26 p.m.