Triple
T21387848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collinsville, Alabama |
E527552
|
entity |
| Predicate | communityCentered |
P76989
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Collinsville, Alabama, communityCentered, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communityCentered Context triple: [Collinsville, Alabama, communityCentered, true]
-
A.
communityService
Indicates participation in activities intended to benefit or support a community, typically performed voluntarily or as a civic responsibility.
-
B.
communityBased
chosen
Indicates that something is organized, developed, or delivered within and by a local community, emphasizing local participation, control, and context.
-
C.
community
Indicates a relationship where individuals or groups are connected by shared location, interests, or identity, forming a collective social unit.
-
D.
communityType
Indicates the classification or category of community to which an entity belongs (e.g., urban, rural, online, professional).
-
E.
communityOrganizations
Indicates that there is an association or involvement between entities and one or more community-based organizations or groups.
- 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_69e0b51ff3748190935c0a513c62a12b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee62cb05288190a894f33850e22c03 |
completed | April 26, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:12 p.m.