Triple
T28662622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idus Martiae |
E725506
|
entity |
| Predicate | hasYearlyRecurrence |
P20895
|
FINISHED |
| Object | annual |
—
|
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: annual | Statement: [Idus Martiae, hasYearlyRecurrence, annual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYearlyRecurrence Context triple: [Idus Martiae, hasYearlyRecurrence, annual]
-
A.
activatedAnnuallyUntil
Indicates that an action or state is activated once each year and continues to do so repeatedly up to, but not beyond, a specified end date.
-
B.
isAnnual
chosen
Indicates that something occurs, is scheduled, or is valid once every year.
-
C.
recurringEndYear
Indicates the calendar year in which a recurring event, pattern, or relationship is scheduled or expected to end.
-
D.
recurringDuring
Indicates that an event or state happens repeatedly within the time span or context defined by another event or interval.
-
E.
recurringEvent
Indicates that an event occurs repeatedly over time according to some regular pattern or schedule.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:59 a.m.