Triple
T23740336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rushikulya rookery, India |
E586655
|
entity |
| Predicate | peakArribadaPeriod |
P153511
|
FINISHED |
| Object | around February to March |
—
|
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: around February to March | Statement: [Rushikulya rookery, India, peakArribadaPeriod, around February to March]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakArribadaPeriod Context triple: [Rushikulya rookery, India, peakArribadaPeriod, around February to March]
-
A.
peakServicePeriod
Indicates the time interval during which a service experiences its highest or most intensive level of use or operation.
-
B.
peakProminencePeriod
Indicates the time period during which something reached its highest level of prominence or significance.
-
C.
peakExportPeriod
Indicates the time period during which exports of a given item or from a given source reach their highest level.
-
D.
peakHours
Indicates that an action, event, or condition occurs during the busiest or most heavily trafficked time period.
-
E.
peakDay
Indicates the specific day on which a quantity, activity, or effect reaches its maximum level within a given period.
- 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_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. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:11 p.m.