Triple
T17522667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crathie |
E426712
|
entity |
| Predicate | parishChurchNotableFor |
P38425
|
FINISHED |
| Object | royal worship services |
—
|
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: royal worship services | Statement: [Crathie, parishChurchNotableFor, royal worship services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishChurchNotableFor Context triple: [Crathie, parishChurchNotableFor, royal worship services]
-
A.
hasParishChurchArchitecturalInterest
Indicates that a parish church possesses notable architectural features or significance.
-
B.
parishChurchFeatures
chosen
Indicates that a parish church possesses or includes specific architectural, artistic, or functional features.
-
C.
isParishChurch
Indicates that a church holds the official status of the main church serving a particular parish within an ecclesiastical jurisdiction.
-
D.
parishChurchName
Indicates the name of the parish church associated with a given entity.
-
E.
isParishChurchIn
Indicates that a church serves as the designated parish church for a specific parish or locality.
- 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_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. |
Created at: April 10, 2026, 5:49 a.m.