Triple
T34727955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiralty Gulf |
E1001122
|
entity |
| Predicate | hasIndigenousNameLanguageGroup |
P124195
|
FINISHED |
| Object | Wunambal |
—
|
NE NERFINISHED |
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: Wunambal | Statement: [Admiralty Gulf, hasIndigenousNameLanguageGroup, Wunambal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndigenousNameLanguageGroup Context triple: [Admiralty Gulf, hasIndigenousNameLanguageGroup, Wunambal]
-
A.
isIndigenousLanguageNameOf
Indicates that a given name is the name of a language as expressed in an indigenous language.
-
B.
isIndigenousLanguageGroup
chosen
Indicates that a language group originates from and is traditionally associated with the native or first peoples of a specific region or territory.
-
C.
hasIndigenousLanguageFamily
Indicates that an entity’s indigenous language belongs to, or is classified under, a particular language family.
-
D.
hasIndigenousLanguageRegion
Indicates that a region is associated with, or characterized by, the presence or use of one or more indigenous languages.
-
E.
indigenousNameOf
Indicates that one entity is the name used for another entity in an indigenous or native language.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a0042524d8c8190884a10fce669ae95 |
completed | May 10, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_6a0041e89bd881909e32764699bcb89b |
completed | May 10, 2026, 8:29 a.m. |
Created at: May 3, 2026, 3:59 p.m.