Triple
T6991171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lycaon pictus |
E162088
|
entity |
| Predicate | offspringCare |
P8768
|
FINISHED |
| Object | alloparental care |
—
|
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: alloparental care | Statement: [Lycaon pictus, offspringCare, alloparental care]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offspringCare Context triple: [Lycaon pictus, offspringCare, alloparental care]
-
A.
parentalCare
chosen
Indicates that one entity provides nurturing, protection, or support to another in a parent-like role.
-
B.
offspringWith
Indicates that two entities share a parent–child relationship, specifying that one is the offspring of the other.
-
C.
adopts
Indicates that one entity formally takes another into its care, control, or use, assuming ongoing responsibility or ownership.
-
D.
offspringType
Indicates the specific kind or category of offspring that results from a parent or reproductive event.
-
E.
offspringGroup
Indicates that one entity is a group or collection composed of the offspring 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbc08758819083d36a1fc0463b27 |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:32 p.m.