Triple
T657994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Callipepla californica |
E11689
|
entity |
| Predicate | breedingSystem |
P8592
|
FINISHED |
| Object | monogamous |
—
|
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: monogamous | Statement: [Callipepla californica, breedingSystem, monogamous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breedingSystem Context triple: [Callipepla californica, breedingSystem, monogamous]
-
A.
reproductionType
Indicates the mode or method by which an organism reproduces or generates offspring.
-
B.
reproductiveType
Indicates the mode or strategy by which an organism reproduces or generates offspring.
-
C.
reproductiveBehavior
chosen
Indicates the actions, strategies, and interactions involved in an organism’s mating and reproduction processes.
-
D.
reproductiveFeature
Indicates a relationship where an entity possesses or is characterized by a particular reproductive trait, structure, or capability.
-
E.
reproductiveStructure
Indicates that one entity serves as a reproductive organ or structure of another, involved in producing or facilitating the formation of offspring or reproductive cells.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fa55e048190bd9913c6c31772d0 |
completed | March 1, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69a49d121cec81909986c91291bb4ca8 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.