Triple
T25146706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arctodus |
E629953
|
entity |
| Predicate | includedSpecies |
P10920
|
FINISHED |
| Object | Arctodus simus |
—
|
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: Arctodus simus | Statement: [Arctodus, includedSpecies, Arctodus simus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedSpecies Context triple: [Arctodus, includedSpecies, Arctodus simus]
-
A.
includesSpecies
chosen
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
-
B.
includesSpeciesFrom
Indicates that one collection, group, or set contains one or more species that originate from or belong to another specified source or context.
-
C.
someSpeciesAre
Indicates that at least one member of a specified group or category belongs to, or can be classified as, a particular species.
-
D.
containsWildSpecies
Indicates that one entity includes, houses, or encompasses wild (non-domesticated) species within its scope or boundaries.
-
E.
notableSpecies
Indicates that the subject is known for, or significantly associated with, 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 18, 2026, 6:30 a.m.