Triple
T31463284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deaf Australians |
E802660
|
entity |
| Predicate | communitySpace |
P173439
|
FINISHED |
| Object | Deaf clubs |
—
|
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: Deaf clubs | Statement: [Deaf Australians, communitySpace, Deaf clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communitySpace Context triple: [Deaf Australians, communitySpace, Deaf clubs]
-
A.
communityAspect
Indicates that something pertains to, reflects, or influences the communal or social dimension of a group or community.
-
B.
community
Indicates a relationship where individuals or groups are connected by shared location, interests, or identity, forming a collective social unit.
-
C.
communityBoard
Indicates a relationship where an entity serves as or is associated with a local governing or advisory community board responsible for representing and addressing community interests.
-
D.
communityType
Indicates the classification or category of community to which an entity belongs (e.g., urban, rural, online, professional).
-
E.
communityOutcome
Indicates the result, impact, or consequence that an action, program, or event has on a community as a whole.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 30, 2026, 9:21 p.m.