Triple
T30070581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirk o’ Field, Edinburgh |
E764170
|
entity |
| Predicate | timePeriodOfUseAsChurch |
P166984
|
FINISHED |
| Object | before and during early 16th century |
—
|
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: before and during early 16th century | Statement: [Kirk o’ Field, Edinburgh, timePeriodOfUseAsChurch, before and during early 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfUseAsChurch Context triple: [Kirk o’ Field, Edinburgh, timePeriodOfUseAsChurch, before and during early 16th century]
-
A.
timePeriodOfWorship
Indicates the specific time period during which the worship activity takes place or is observed.
-
B.
usePeriodAsChurch
chosen
Indicates that a particular time period is used or designated for church-related activities or functions.
-
C.
usedAsChurchUntil
Indicates that something served the function or role of a church up to a specified point in time.
-
D.
usedAsChurchFrom
Indicates that something functioned or was utilized as a church starting from a specified point in time.
-
E.
worshipPeriod
Indicates the time span or specific period during which an act of worship or religious devotion takes place.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 29, 2026, 7 p.m.