Triple
T18485331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirounga |
E451673
|
entity |
| Predicate | hasCommonNameForTaxon |
P77570
|
FINISHED |
| Object | southern elephant seal |
—
|
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: southern elephant seal | Statement: [Mirounga, hasCommonNameForTaxon, southern elephant seal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonNameForTaxon Context triple: [Mirounga, hasCommonNameForTaxon, southern elephant seal]
-
A.
hasSurroundingTreeCommonName
Indicates that an entity is associated with a surrounding tree identified by its common (vernacular) name.
-
B.
hasTribeCommonName
Indicates that two entities are related by the commonly used (vernacular) name of a tribe.
-
C.
hasRelatedTaxon
Indicates a taxonomic relationship between two taxa that are connected in some biologically or taxonomically relevant way, without specifying the exact nature of that relationship.
-
D.
includesSpeciesCommonName
chosen
Indicates that an entity contains or specifies the common (vernacular) name of a species.
-
E.
hasClassifiedTaxon
Indicates that an entity has assigned or associated a specific taxonomic classification to 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d6502c8190af167b954bf8e989 |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.