Triple
T24758297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gedaged people |
E619353
|
entity |
| Predicate | areIndigenousToMadangCoast |
P122485
|
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: [Gedaged people, areIndigenousToMadangCoast, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areIndigenousToMadangCoast Context triple: [Gedaged people, areIndigenousToMadangCoast, true]
-
A.
refersToIndigenousPeopleOf
chosen
Indicates that one entity is about, concerns, or designates the indigenous people associated with another entity.
-
B.
islandDwellers
Indicates that the related entities are inhabitants or residents of an island.
-
C.
hasIndigenousGroupInIsolation
Indicates that an indigenous group exists within a region or context while remaining in isolation from the broader society or external contact.
-
D.
riverinePeople
Indicates a relationship where people live along, depend on, or are closely associated with rivers and river environments.
-
E.
recognizedAsIndigenousPeopleBy
Indicates that one party formally acknowledges and accepts another party as belonging to an indigenous people or 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:26 a.m.