Triple
T2699797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abyssinian Baptist Church |
E59202
|
entity |
| Predicate | hasMainBuildingAddress |
P4379
|
FINISHED |
| Object | 132 Odell Clark Place |
—
|
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: 132 Odell Clark Place | Statement: [Abyssinian Baptist Church, hasMainBuildingAddress, 132 Odell Clark Place]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainBuildingAddress Context triple: [Abyssinian Baptist Church, hasMainBuildingAddress, 132 Odell Clark Place]
-
A.
isMainBuildingOf
Indicates that a building serves as the primary or central facility associated with a particular organization, complex, or site.
-
B.
hasMainStreet
Indicates that a place or locality possesses a primary street commonly recognized as its main thoroughfare.
-
C.
hasAddress
chosen
Indicates that an entity is associated with a specific address or location.
-
D.
hasHeadquartersBuilding
Indicates that an organization possesses a specific building that serves as its headquarters location.
-
E.
hasMainLocationType
Indicates that an entity is associated with a primary or predominant type of location that characterizes where it is mainly situated or operates.
- 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda34ba508190be8e2c9e4052adfc |
completed | March 7, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.