Triple
T248172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | harpy eagle |
E5082
|
entity |
| Predicate | parentalCare |
P8768
|
FINISHED |
| Object | biparental |
—
|
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: biparental | Statement: [harpy eagle, parentalCare, biparental]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentalCare Context triple: [harpy eagle, parentalCare, biparental]
-
A.
parents
Indicates a parental relationship where one entity is the mother or father of another entity.
-
B.
parent
Indicates a relationship where one entity is the direct mother or father of another entity, from whom that other entity is descended.
-
C.
peacetimeParent
Indicates that one entity is recognized as the parent of another during periods of peace, as opposed to wartime or conflict conditions.
-
D.
children
Indicates that one entity is the offspring or direct descendant of another entity.
-
E.
familyControlled
Indicates that an entity is owned or effectively governed by one or more members of the same family, who hold decisive control over its decisions or operations.
- F. None of above. chosen
Provenance (4 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d154ebc819087a5c9dc4f62ff44 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b64ea3081908de626a0e1445bdb |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c2ca46c81908c61696f31e59a98 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.