Triple
T26487210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gagaʻemauga |
E664853
|
entity |
| Predicate | hasVillageCluster |
P165354
|
FINISHED |
| Object | group of villages on Savaiʻi |
—
|
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: group of villages on Savaiʻi | Statement: [Gagaʻemauga, hasVillageCluster, group of villages on Savaiʻi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVillageCluster Context triple: [Gagaʻemauga, hasVillageCluster, group of villages on Savaiʻi]
-
A.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
-
B.
isVillage
Indicates that the subject entity is classified as a village, typically a small human settlement or community.
-
C.
hasVillageAccess
Indicates that an entity is permitted to enter, use, or benefit from the facilities, services, or areas of a particular village.
-
D.
hasUrbanVillages
Indicates that an entity contains or includes one or more designated urban villages within its area or jurisdiction.
-
E.
isInVillage
Indicates that one entity is located within or belongs to the area defined as a village in relation to another entity.
- 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 27, 2026, 12:31 a.m.