Triple
T36801262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamatji |
E909326
|
entity |
| Predicate | hasCommunityHub |
P73098
|
FINISHED |
| Object | Geraldton |
E55090
|
NE 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: Geraldton | Statement: [Yamatji, hasCommunityHub, Geraldton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityHub Context triple: [Yamatji, hasCommunityHub, Geraldton]
-
A.
isCommunityHub
chosen
Indicates that a place or entity functions as a central gathering point or focal location for community activities, services, and interactions.
-
B.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
C.
hasCommunitySpace
Indicates that an entity provides or includes a shared physical or virtual area intended for communal use, activities, or gatherings.
-
D.
hasCommunitySupport
Indicates that an entity is backed, endorsed, or positively received by a community or group of users.
-
E.
hasCommunityGroup
Indicates that an entity is associated with, or belongs to, a specific community group.
- F. None of above.
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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3d17aff38c8190ab87df259c2ccd6f |
completed | June 25, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.