Triple
T12052085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Booby Pond Nature Reserve |
E286940
|
entity |
| Predicate | hasResidentSpecies |
P6481
|
FINISHED |
| Object | red-footed booby |
—
|
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: red-footed booby | Statement: [Booby Pond Nature Reserve, hasResidentSpecies, red-footed booby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidentSpecies Context triple: [Booby Pond Nature Reserve, hasResidentSpecies, red-footed booby]
-
A.
hasNativeSpecies
Indicates that a particular species naturally occurs and evolved in a specified geographic area or habitat, rather than being introduced from elsewhere.
-
B.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
-
C.
inhabitedBy
chosen
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
-
D.
hasCommonSpecies
Indicates that two entities share at least one species in common.
-
E.
hasWildPopulationOf
Indicates that a location or area contains a naturally occurring, non-captive population of the specified species.
- 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bac9e08190aa1a99c835f29542 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.