Triple
T1644382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterboat Point |
E35545
|
entity |
| Predicate | hasNestingSpecies |
P10920
|
FINISHED |
| Object | gentoo penguin |
—
|
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: gentoo penguin | Statement: [Waterboat Point, hasNestingSpecies, gentoo penguin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNestingSpecies Context triple: [Waterboat Point, hasNestingSpecies, gentoo penguin]
-
A.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
-
B.
includesSpecies
chosen
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
-
C.
hasInvasiveSpecies
Indicates that an area, ecosystem, or habitat contains one or more species that are non-native and causing or likely to cause ecological, economic, or environmental harm.
-
D.
hasBiodiversityFeature
Indicates that an entity possesses or is associated with a specific biodiversity-related characteristic, attribute, or element.
-
E.
isMajorHabitatFor
Indicates that one entity serves as a primary or significant natural living environment for another entity.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a919306fd48190a245fc95e0e759d9 |
completed | March 5, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69a907cc9d348190b76b0d3f596e5a81 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.