Triple
T23740400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ostional, Costa Rica |
E586656
|
entity |
| Predicate | arribadasFrequency |
P153513
|
FINISHED |
| Object | several times per year |
—
|
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: several times per year | Statement: [Ostional, Costa Rica, arribadasFrequency, several times per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arribadasFrequency Context triple: [Ostional, Costa Rica, arribadasFrequency, several times per year]
-
A.
arribadaDefinition
Indicates a mass, synchronized arrival or landing of many individuals of a species—typically sea turtles—at a specific location for nesting or reproduction.
-
B.
boreTideFrequency
Indicates how often a tidal bore occurs within a given time period.
-
C.
laterFrequency
Indicates that one event, state, or action occurs with a lower frequency than another in a temporal sequence.
-
D.
stormPeriodicity
Indicates the regularity or recurrence pattern with which storms occur over time.
-
E.
encounterFrequency
Indicates how often two entities come into contact or interact with each other over 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.