Triple
T2293142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chatham, Chicago |
E51549
|
entity |
| Predicate | hasCommunityInstitutions |
P39016
|
FINISHED |
| Object | churches |
—
|
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: churches | Statement: [Chatham, Chicago, hasCommunityInstitutions, churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityInstitutions Context triple: [Chatham, Chicago, hasCommunityInstitutions, churches]
-
A.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
B.
hasStateInstitution
Indicates that a particular state possesses, governs, or is served by a specific institution operating under its authority or within its jurisdiction.
-
C.
establishedInstitution
Indicates that an entity founded, created, or formally set up an institution or organization.
-
D.
hasCulturalCommunity
Indicates that an entity is associated with, belongs to, or is part of a specific cultural community.
-
E.
includesCommunity
Indicates that one entity encompasses, contains, or has within it a particular community as part of its scope or composition.
- 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcd0e42248190ada33b84d75caa64 |
completed | March 7, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69abc589295c819092989820c2b4e9d8 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abcd0d01ac8190935fe904905cb233 |
completed | March 7, 2026, 7 a.m. |
Created at: March 4, 2026, 7:48 p.m.