Triple
T38509216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samuel Seabury |
E921854
|
entity |
| Predicate | consecrationPlace |
P43645
|
FINISHED |
| Object | Aberdeen, Scotland |
—
|
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: Aberdeen, Scotland | Statement: [Samuel Seabury, consecrationPlace, Aberdeen, Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consecrationPlace Context triple: [Samuel Seabury, consecrationPlace, Aberdeen, Scotland]
-
A.
placeOfConsecration
chosen
Indicates the specific place where a religious or ceremonial consecration of something or someone took place.
-
B.
consecratedBy
Indicates that one entity has been formally made sacred, dedicated, or set apart for religious use through a ritual or act performed by another entity.
-
C.
veneratedAt
Indicates that an entity is honored, revered, or worshipped at a particular place or institution.
-
D.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
-
E.
consecratedInPresenceOf
Indicates that the act of consecration was performed while a specified person, group, or entity was present as a witness or participant.
- 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_69f76ea3c5448190aa7002fc1ba3f874 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 3, 2026, 4:32 p.m.