Triple
T36261564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Caledonia Time |
E892100
|
entity |
| Predicate | usedInOceanRegion |
P136583
|
FINISHED |
| Object | Southwest Pacific Ocean |
—
|
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: Southwest Pacific Ocean | Statement: [New Caledonia Time, usedInOceanRegion, Southwest Pacific Ocean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInOceanRegion Context triple: [New Caledonia Time, usedInOceanRegion, Southwest Pacific Ocean]
-
A.
belongsToOceanicRegion
chosen
Indicates that one entity is geographically or administratively situated within, or associated with, a specified oceanic region.
-
B.
hasOceanSubregion
Indicates that a larger oceanic area is divided into or associated with a more specific subregion within it.
-
C.
hasPrimaryOceanRegion
Indicates that an entity is primarily associated with or located within a specified ocean region as its main marine area.
-
D.
oceanPresence
Indicates that an entity is located in, adjacent to, or significantly influenced by an ocean.
-
E.
isInSeaRegion
Indicates that one entity (typically a location or object) is situated within the boundaries of a specified sea region.
- 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_69f76e4699188190af045b11a840ce31 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: May 3, 2026, 4:09 p.m.