Triple
T30336231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | red-billed tropicbird |
E771627
|
entity |
| Predicate | parentalCareBy |
P8768
|
FINISHED |
| Object | both parents |
—
|
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: both parents | Statement: [red-billed tropicbird, parentalCareBy, both parents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentalCareBy Context triple: [red-billed tropicbird, parentalCareBy, both parents]
-
A.
parentalCare
chosen
Indicates that one entity provides nurturing, protection, or support to another in a parent-like role.
-
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.
parentalCharacter
Indicates a relationship where one entity exhibits traits, behaviors, or qualities characteristic of a parent toward another entity.
-
D.
parents
Indicates a parental relationship where one entity is the mother or father of another entity.
-
E.
unwillingParentOf
Indicates a parental relationship in which the parent does not willingly or voluntarily assume the role or responsibilities toward the child.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 29, 2026, 7:54 p.m.