Triple
T1571931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | zebra finch |
E33558
|
entity |
| Predicate | breeding |
P8592
|
FINISHED |
| Object | opportunistic breeder in response to rainfall |
—
|
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: opportunistic breeder in response to rainfall | Statement: [zebra finch, breeding, opportunistic breeder in response to rainfall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breeding Context triple: [zebra finch, breeding, opportunistic breeder in response to rainfall]
-
A.
breedingMethod
Indicates the technique or process by which organisms are bred or reproduced.
-
B.
reproductiveBehavior
chosen
Indicates the actions, strategies, and interactions involved in an organism’s mating and reproduction processes.
-
C.
breed
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
-
D.
breeder
Indicates that an entity is responsible for producing, raising, or propagating another entity, typically through controlled reproduction.
-
E.
reproductionInCaptivity
Indicates that an organism reproduces successfully while being kept in a controlled or captive environment rather than in the wild.
- 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_69a885f11b048190935025a035302715 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907ba63c88190b60c14dec8d1e40f |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.