Triple
T35458219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southside Place, Texas |
E1024837
|
entity |
| Predicate | isInnerLoopCommunity |
P183311
|
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: [Southside Place, Texas, isInnerLoopCommunity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInnerLoopCommunity Context triple: [Southside Place, Texas, isInnerLoopCommunity, true]
-
A.
isCommunity
Indicates that an entity functions as or is classified as a community, typically representing a group of individuals connected by shared location, interests, or characteristics.
-
B.
isCommunityBy
Indicates that something functions as or is recognized as a community defined or established by a particular agent or source.
-
C.
isRemoteCommunity
Indicates that a community is geographically isolated or distant from urban centers and services.
-
D.
isCommunityOf
Indicates that one entity functions as a community composed of, or defined by, the members or elements represented by the other entity.
-
E.
isCommunityRun
Indicates that something is managed, operated, or governed collectively by members of a community rather than by an external or centralized authority.
- 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_69f76df92f108190817222e520e22268 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:04 p.m.