Triple
T25228914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tremarctos |
E632169
|
entity |
| Predicate | isOnlyLivingNativeBearGenusOf |
P56912
|
FINISHED |
| Object | South America |
—
|
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 America | Statement: [Tremarctos, isOnlyLivingNativeBearGenusOf, South America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnlyLivingNativeBearGenusOf Context triple: [Tremarctos, isOnlyLivingNativeBearGenusOf, South America]
-
A.
onlyNativeBearOf
Indicates that one entity is the sole bear species naturally occurring in the specified geographic region or habitat.
-
B.
containsOnlyExtantBearSpecies
Indicates that the set or collection in question includes exclusively bear species that are currently extant (not extinct), with no extinct bear species present.
-
C.
isBear
Indicates that the subject is classified as a bear.
-
D.
isOnlyGenusIn
chosen
Indicates that a genus is the sole genus contained within a specified higher-level taxonomic group or context.
-
E.
basedOnAnimalNativeTo
Indicates that something is derived from, inspired by, or modeled after an animal that is native to a specified geographic region.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47cc608bc8190b3ae866dafd25c4f |
completed | May 1, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:04 p.m.