Triple
T8684764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MARCH |
E206129
|
entity |
| Predicate | hasReligiousBuilding |
P1191
|
FINISHED |
| Object | St Peter’s Church |
unclear NED1
|
NE 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: St Peter’s Church | Statement: [MARCH, hasReligiousBuilding, St Peter’s Church]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: St Peter’s Church Context triple: [MARCH, hasReligiousBuilding, St Peter’s Church]
-
A.
St Peter’s Church
St Peter’s Church is a Christian place of worship serving the local community in West Molesey, England.
-
B.
St Peter’s Church
St Peter’s Church is the principal Anglican parish church serving the village community of Chalfont St Peter in Buckinghamshire, England.
-
C.
St Peter’s Church
St Peter’s Church is a historic Anglican parish church serving the rural community of Langwathby in Cumbria, England.
-
D.
St Peter's Church
St Peter's Church is a historic medieval Lutheran church in Riga, Latvia, renowned for its towering spire and panoramic city views.
-
E.
Church of St Peter
The Church of St Peter is a historic Christian parish church serving the village of Cornwell in England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4aeae740819099093906ccc5f640 |
completed | March 31, 2026, 10:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf6ed1e0548190b02d43c5d7e65e08 |
completed | April 3, 2026, 7:40 a.m. |
Created at: March 30, 2026, 6:32 p.m.