Triple
T22935064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paleotropical floristic region |
E569557
|
entity |
| Predicate | oceanicRegionCoverage |
P150310
|
FINISHED |
| Object | Pacific Ocean islands |
—
|
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: Pacific Ocean islands | Statement: [Paleotropical floristic region, oceanicRegionCoverage, Pacific Ocean islands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oceanicRegionCoverage Context triple: [Paleotropical floristic region, oceanicRegionCoverage, Pacific Ocean islands]
-
A.
oceanicPortion
Indicates that one entity is a part or segment of an ocean or oceanic area in relation to another entity.
-
B.
hasOceanSubregion
Indicates that a larger oceanic area is divided into or associated with a more specific subregion within it.
-
C.
oceanBasin
Indicates a relationship where a geographic or marine feature is located within, or is part of, a specific ocean basin.
-
D.
hasOceanCoverage
Indicates that a specified area or region is covered by ocean to a certain extent or proportion.
-
E.
belongsToOceanicRegion
Indicates that one entity is geographically or administratively situated within, or associated with, a specified oceanic region.
- 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181350c7881908a72dc7a30e1aaff |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:44 p.m.