Triple
T38531400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smooth-billed ani |
E923374
|
entity |
| Predicate | hasBreedingBehavior |
P8592
|
FINISHED |
| Object | cooperative breeding |
—
|
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: cooperative breeding | Statement: [Smooth-billed ani, hasBreedingBehavior, cooperative breeding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBreedingBehavior Context triple: [Smooth-billed ani, hasBreedingBehavior, cooperative breeding]
-
A.
hasBreedingFocus
Indicates that an entity is the primary target or subject of another entity’s breeding efforts or breeding program.
-
B.
reproductiveBehavior
chosen
Indicates the actions, strategies, and interactions involved in an organism’s mating and reproduction processes.
-
C.
hasBreedingMechanicIntroduced
Indicates that a breeding-related game mechanic has been introduced or made available within the system or context.
-
D.
breedingType
Indicates the method or strategy by which organisms reproduce or are bred.
-
E.
supportsBreeding
Indicates that one entity enables, facilitates, or is suitable for the breeding or reproduction of 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 3, 2026, 4:32 p.m.