Triple
T23740335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rushikulya rookery, India |
E586655
|
entity |
| Predicate | hasNestingSeason |
P29852
|
FINISHED |
| Object | roughly December to April |
—
|
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: roughly December to April | Statement: [Rushikulya rookery, India, hasNestingSeason, roughly December to April]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNestingSeason Context triple: [Rushikulya rookery, India, hasNestingSeason, roughly December to April]
-
A.
hasSeasonalSpecies
Indicates that certain species are present or occur only during specific seasons in relation to a given context or location.
-
B.
breedingSeasonsPerYear
Indicates how many distinct breeding periods an organism has within a single year.
-
C.
reproductionSeason
chosen
Indicates the time period or season during which an organism typically engages in reproductive activity.
-
D.
hasBreedingFocus
Indicates that an entity is the primary target or subject of another entity’s breeding efforts or breeding program.
-
E.
hasSeason
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad5209081909c44380816bec377 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:11 p.m.