Triple
T17522665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crathie |
E426712
|
entity |
| Predicate | parishChurchReplaced |
P127797
|
FINISHED |
| Object | earlier 18th-century church |
—
|
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: earlier 18th-century church | Statement: [Crathie, parishChurchReplaced, earlier 18th-century church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishChurchReplaced Context triple: [Crathie, parishChurchReplaced, earlier 18th-century church]
-
A.
usedAsChurchUntil
Indicates that something served the function or role of a church up to a specified point in time.
-
B.
originalChurchDestroyed
Indicates that the initially established church building was demolished or ceased to exist, typically due to destruction rather than relocation or replacement.
-
C.
usedAsChurchFrom
Indicates that something functioned or was utilized as a church starting from a specified point in time.
-
D.
hasReconstructedChurch
Indicates that an entity has rebuilt or restored a church, typically after damage, destruction, or disuse.
-
E.
formerCathedral
Indicates that a building once held the status and function of a cathedral but no longer does.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d40ee08190b79d8e3d7f1b1272 |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:49 a.m.