Triple
T36929835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Binding of the Years |
E913447
|
entity |
| Predicate | performedAtInterval |
P16914
|
FINISHED |
| Object | every 52 years |
—
|
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: every 52 years | Statement: [Binding of the Years, performedAtInterval, every 52 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedAtInterval Context triple: [Binding of the Years, performedAtInterval, every 52 years]
-
A.
performedFrequency
chosen
Indicates how often an action or activity is carried out within a given time period.
-
B.
usesInterval
Indicates that one entity operates, functions, or is defined within a specific time or value interval associated with another entity.
-
C.
hasInterval
Indicates that something is associated with a specific span or range between two points in time, space, or value.
-
D.
intervalAct
Indicates an action or relationship that occurs over, or is defined by, a specific time interval between entities.
-
E.
performsAt
Indicates that an entity carries out or presents a performance at a specific location, venue, or event.
- 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
Created at: May 3, 2026, 4:13 p.m.