Triple
T26559922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eddleston |
E666208
|
entity |
| Predicate | parishChurchBuildingMaterial |
P134857
|
FINISHED |
| Object | stone |
—
|
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: stone | Statement: [Eddleston, parishChurchBuildingMaterial, stone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishChurchBuildingMaterial Context triple: [Eddleston, parishChurchBuildingMaterial, stone]
-
A.
parishChurchConstructionMaterial
chosen
Indicates the material from which a parish church is constructed.
-
B.
parishChurchArchitectureStyle
Indicates the architectural style or design tradition in which a parish church is built or characterized.
-
C.
materialOfChapelRuins
Indicates that a specified material was used in the construction of the chapel whose remains or ruins are being described.
-
D.
parishChurchFeatures
Indicates that a parish church possesses or includes specific architectural, artistic, or functional features.
-
E.
isParishChurch
Indicates that a church holds the official status of the main church serving a particular parish within an ecclesiastical jurisdiction.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6146b58f4819082de70318c588211 |
completed | May 2, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:52 a.m.