Triple
T6328976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bugotu language |
E141927
|
entity |
| Predicate | hasOceanicAncestor |
P34787
|
FINISHED |
| Object | Proto-Oceanic language |
—
|
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: Proto-Oceanic language | Statement: [Bugotu language, hasOceanicAncestor, Proto-Oceanic language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOceanicAncestor Context triple: [Bugotu language, hasOceanicAncestor, Proto-Oceanic language]
-
A.
hasOcean
Indicates that a geographic region, country, or landmass is bordered by or directly adjacent to a particular ocean.
-
B.
hasAncestralRoots
chosen
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
C.
hasOceanicCrustAlong
Indicates that an entity possesses or is characterized by oceanic crust extending along a specified boundary, feature, or region.
-
D.
hasHomininTaxon
Indicates that an entity is associated with, classified under, or belongs to a particular hominin taxonomic group.
-
E.
belongsToOcean
Indicates that a body of water or coastal region is part of, contained within, or directly associated with a particular ocean.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0651197908190a30e504e2442d40f |
completed | March 22, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.