Triple
T15695749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nazca booby |
E380454
|
entity |
| Predicate | siblingInteraction |
P42188
|
FINISHED |
| Object | obligate siblicide common in broods |
—
|
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: obligate siblicide common in broods | Statement: [Nazca booby, siblingInteraction, obligate siblicide common in broods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siblingInteraction Context triple: [Nazca booby, siblingInteraction, obligate siblicide common in broods]
-
A.
siblingRival
chosen
Indicates a relationship where two siblings are in competition or conflict with each other.
-
B.
sibling
Indicates that two entities share at least one parent, making them brothers or sisters to each other.
-
C.
stepSibling
Indicates that two people share at least one parent but do not share both biological parents, making them step-siblings.
-
D.
interFamilyRelations
Indicates relationships or interactions that occur between different families or family units.
-
E.
parentalIssue
Indicates that there is a problem, conflict, or difficulty involving a person's relationship or situation with their parent(s).
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:44 a.m.