Triple
T8092211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jarvis Island |
E188892
|
entity |
| Predicate | hasMainHabitats |
P14557
|
FINISHED |
| Object | seabird nesting areas |
—
|
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: seabird nesting areas | Statement: [Jarvis Island, hasMainHabitats, seabird nesting areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainHabitats Context triple: [Jarvis Island, hasMainHabitats, seabird nesting areas]
-
A.
isMajorHabitatFor
chosen
Indicates that one entity serves as a primary or significant natural living environment for another entity.
-
B.
hasNativeSpecies
Indicates that a particular species naturally occurs and evolved in a specified geographic area or habitat, rather than being introduced from elsewhere.
-
C.
hasNearbyHabitats
Indicates that one entity has other habitats located close to it in geographic or spatial terms.
-
D.
simulatesHabitatOf
Indicates that one entity artificially recreates or models the living conditions or environment characteristic of another entity’s natural habitat.
-
E.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
- 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_69ca82b7b3e88190b9041ab0ef28b3cb |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb42217a1881909792b08a2f06fb75 |
completed | March 31, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:30 p.m.