Triple
T23899639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stair, Ayrshire |
E601004
|
entity |
| Predicate | hasFormerChurch |
P15000
|
FINISHED |
| Object | Old Stair Church |
—
|
NE NERFINISHED |
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: Old Stair Church | Statement: [Stair, Ayrshire, hasFormerChurch, Old Stair Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerChurch Context triple: [Stair, Ayrshire, hasFormerChurch, Old Stair Church]
-
A.
usedAsChurchFrom
Indicates that something functioned or was utilized as a church starting from a specified point in time.
-
B.
usedAsChurchUntil
Indicates that something served the function or role of a church up to a specified point in time.
-
C.
earlierChurchUsedBy
Indicates that one church building was used by a group or congregation before they used another, later church building.
-
D.
hasChurch
chosen
Indicates that a place or entity possesses, contains, or is associated with a church.
-
E.
hasParentChurch
Indicates that a church or religious organization is institutionally subordinate to or derived from another church, which serves as its parent or overseeing body.
- 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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cddca9708190acd3e9edc9b5940b |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:25 p.m.