Triple
T28996858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIThenge |
E736188
|
entity |
| Predicate | occursApproximately |
P39845
|
FINISHED |
| Object | twice a 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: twice a year | Statement: [MIThenge, occursApproximately, twice a year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursApproximately Context triple: [MIThenge, occursApproximately, twice a year]
-
A.
containsApproximately
Indicates that one entity holds or includes another entity in a quantity or proportion that is close to, but not exactly, a specified amount.
-
B.
occursOnOrAround
chosen
Indicates that an event or action takes place on a specific date or within a small, approximate time window surrounding that date.
-
C.
representsApproximately
Indicates that one entity serves as an inexact or close-but-not-exact representation or value of another entity.
-
D.
holdsApproximatelyFor
Indicates that a condition, relation, or value is valid only to an approximate degree or within a tolerance, rather than holding exactly.
-
E.
runsApproximately
Indicates that an entity performs a running action in a manner that is close to, but not exactly matching, a specified time, distance, speed, or other running-related measure.
- 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_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 9:31 a.m.