Triple
T35595940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bunnacurry |
E1028630
|
entity |
| Predicate | hasTraditionalIslandCommunity |
P46548
|
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: [Bunnacurry, hasTraditionalIslandCommunity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalIslandCommunity Context triple: [Bunnacurry, hasTraditionalIslandCommunity, true]
-
A.
isTraditionalIslandCommunityOf
Indicates that one entity is recognized as the traditional island-based community associated with, originating from, or historically belonging to another entity.
-
B.
isIslandCommunity
Indicates that a community is located on an island and is geographically separated from mainland areas.
-
C.
hasTraditionalCommunity
chosen
Indicates that an entity possesses or is associated with a community that maintains traditional practices, customs, or ways of life.
-
D.
hasTribalCommunities
Indicates that an entity possesses, includes, or is associated with one or more tribal communities.
-
E.
isIslandCommunityCenter
Indicates that a location functions as the primary communal hub or gathering place for an island community.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:05 p.m.