Triple
T23601303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | southern elephant seal |
E582763
|
entity |
| Predicate | majorBreedingColony |
P131847
|
FINISHED |
| Object | South Georgia |
—
|
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: South Georgia | Statement: [southern elephant seal, majorBreedingColony, South Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorBreedingColony Context triple: [southern elephant seal, majorBreedingColony, South Georgia]
-
A.
notableBreedingColony
chosen
Indicates that an entity serves as a significant or well-known site where a particular species regularly breeds or nests.
-
B.
breedingCenter
Indicates a relationship where an entity serves as a facility or location dedicated to breeding or reproducing organisms.
-
C.
colonyOf
Indicates that one entity is a colony belonging to, founded by, or politically dependent on another entity.
-
D.
colonyLocatedIn
Indicates that a colony is geographically or administratively situated within a specified larger area or jurisdiction.
-
E.
hostsColonyOf
Indicates that one entity serves as the living site or environment in which a colony of another entity resides or is established.
- 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_69e248faa2788190abb1581742daa6aa |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b0947bd8819097e26643dc257dc0 |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:43 p.m.