Triple
T27504623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aptenodytes forsteri |
E694246
|
entity |
| Predicate | incubationRole |
P23046
|
FINISHED |
| Object | male incubates egg on feet |
—
|
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: male incubates egg on feet | Statement: [Aptenodytes forsteri, incubationRole, male incubates egg on feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incubationRole Context triple: [Aptenodytes forsteri, incubationRole, male incubates egg on feet]
-
A.
inceptionAsRole
Indicates the point in time or event at which an entity first assumes or begins serving in a particular role or capacity.
-
B.
engagementRole
Indicates the specific function, capacity, or responsibility an entity assumes within a particular engagement or interaction.
-
C.
adoptionRole
Indicates the specific role an entity plays within an adoption relationship, such as adopter, adoptee, or intermediary.
-
D.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
E.
reproductiveRole
chosen
Indicates the specific function or part an entity plays in biological reproduction within a reproductive process or system.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62ec57824819093909e9a5f04a592 |
completed | May 2, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:13 p.m.