Triple
T28996884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIThenge |
E736188
|
entity |
| Predicate | hasRecurrencePattern |
P112554
|
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: [MIThenge, hasRecurrencePattern, annual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecurrencePattern Context triple: [MIThenge, hasRecurrencePattern, annual]
-
A.
hasRecurringElement
Indicates that an entity includes an element that appears repeatedly or occurs multiple times within it.
-
B.
hasRepetition
Indicates that something occurs, appears, or is performed more than once, showing recurrence or repeated instances within a given context.
-
C.
recurrenceType
chosen
Indicates the pattern or frequency with which an event or action repeats over time.
-
D.
definesRecurrenceFor
Indicates that one entity specifies or establishes the recurrence pattern or schedule that applies to another entity.
-
E.
recurringDuring
Indicates that an event or state happens repeatedly within the time span or context defined by another event or interval.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ffaa7bc45c8190b907db8579244a7b |
completed | May 9, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69ffa9f6c9a481908fbd4d18b311cbe2 |
completed | May 9, 2026, 9:41 p.m. |
Created at: April 28, 2026, 9:31 a.m.