Triple
T6175326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Cancrids |
E137802
|
entity |
| Predicate | occurrenceFrequency |
P53048
|
FINISHED |
| Object | once 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: once per year | Statement: [Delta Cancrids, occurrenceFrequency, once per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occurrenceFrequency Context triple: [Delta Cancrids, occurrenceFrequency, once per year]
-
A.
frequencyComparedTo
Indicates how often one event or action occurs relative to another, expressing a comparison of their frequencies.
-
B.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
C.
frequencyClass
chosen
Indicates how often an event, action, or relation occurs, typically by assigning it to a predefined frequency category or class.
-
D.
notableFrequency
Indicates that an action, event, or occurrence happens with a frequency that is significant or noteworthy compared to typical expectations.
-
E.
isFrequentlyIncludedIn
Indicates that something is regularly or commonly contained or made part of something else.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dc55b5c819084482b735771c9a8 |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.