Triple
T3060111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park Street Church |
E60576
|
entity |
| Predicate | hasParishHouse |
P44856
|
FINISHED |
| Object | adjacent building on Park Street |
—
|
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: adjacent building on Park Street | Statement: [Park Street Church, hasParishHouse, adjacent building on Park Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishHouse Context triple: [Park Street Church, hasParishHouse, adjacent building on Park Street]
-
A.
hasParishCommunity
Indicates that an entity is associated with, served by, or belongs to a specific parish community.
-
B.
hasParishCouncils
Indicates that an entity possesses, is served by, or is administratively associated with one or more parish councils.
-
C.
parishIncludes
Indicates that a parish geographically or administratively contains or encompasses another entity or area.
-
D.
hasParishType
Indicates that an entity is associated with or classified by a specific type or category of parish.
-
E.
hasPublicHouse
Indicates that one entity possesses, operates, or is associated with a public house (such as a bar or pub) as part of its facilities or holdings.
- F. None of above. chosen
Provenance (4 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9e9cf9188190b43f50edc009030d |
completed | March 8, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69ad962326e081909d5521c3d3ea3158 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3:02 p.m.