Triple
T3666267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Masarinae |
E77764
|
entity |
| Predicate | reproductiveCare |
P50254
|
FINISHED |
| Object | nest provisioning for offspring |
—
|
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: nest provisioning for offspring | Statement: [Masarinae, reproductiveCare, nest provisioning for offspring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reproductiveCare Context triple: [Masarinae, reproductiveCare, nest provisioning for offspring]
-
A.
reproductiveSystem
Indicates a relationship where one entity is the reproductive system of another, responsible for producing offspring or reproductive cells.
-
B.
sexControlTechnique
Indicates a technique or method used to influence, determine, or manipulate the sex of organisms or offspring.
-
C.
fertility
Indicates the capacity or potential of an entity to reproduce or generate offspring.
-
D.
conceptionBy
Indicates that one entity is conceived or brought into existence by another entity.
-
E.
reproductiveRole
Indicates the specific function or part an entity plays in biological reproduction within a reproductive process or system.
- 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_69ad85dfc4dc8190a441864202ab2a7a |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc40188988190b1b7ac9c8240a5ff |
completed | March 8, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69adb847e9d881909dad2ffd0f3b6c15 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb97cdb788190a5ce96b21bd157ab |
completed | March 8, 2026, 6:01 p.m. |
Created at: March 8, 2026, 3:25 p.m.