Triple
T30502322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of the Covenant, Boston, Massachusetts |
E776168
|
entity |
| Predicate | cornerWith |
P26784
|
FINISHED |
| Object | Berkeley Street |
—
|
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: Berkeley Street | Statement: [Church of the Covenant, Boston, Massachusetts, cornerWith, Berkeley Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cornerWith Context triple: [Church of the Covenant, Boston, Massachusetts, cornerWith, Berkeley Street]
-
A.
cornerOfTriangle
Indicates that the subject is a vertex (corner point) belonging to a specific triangle.
-
B.
hasCorner
Indicates that one entity possesses or includes a corner that is part of or associated with another entity.
-
C.
locatedAtCornerOf
chosen
Indicates that one entity is positioned at or forms the corner where two or more boundaries, edges, or intersecting paths meet.
-
D.
cornerRepresents
Indicates that a particular corner in a structure, diagram, or space stands for or symbolizes another element, concept, or feature.
-
E.
cornerComplexType
Indicates a relationship where something is positioned, formed, or structured at or around a corner in a complex or composite manner.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687812a6481908b126c0aacd38936 |
completed | May 2, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:15 p.m.