Triple
T18258715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tretten Church |
E437287
|
entity |
| Predicate | earlierChurchLocation |
P27687
|
FINISHED |
| Object | same site in Tretten |
—
|
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: same site in Tretten | Statement: [Tretten Church, earlierChurchLocation, same site in Tretten]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierChurchLocation Context triple: [Tretten Church, earlierChurchLocation, same site in Tretten]
-
A.
earlierChurchOnSite
chosen
Indicates that an earlier church building previously existed on the same site as the referenced church or structure.
-
B.
foundingLocationOfChurch
Indicates the place where a particular church was originally founded or established.
-
C.
formerCathedralLocatedIn
Indicates that a building which previously served as a cathedral is located within a specified place or region.
-
D.
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.
-
E.
oldCathedralNearby
Indicates that an old cathedral is located close to a given reference point or entity.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd8879e88190893f8da7c3529496 |
completed | April 19, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.