Triple
T35913280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | summer solstice |
E1038678
|
entity |
| Predicate | variesDueTo |
P173847
|
FINISHED |
| Object | leap 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: leap years | Statement: [summer solstice, variesDueTo, leap years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: variesDueTo Context triple: [summer solstice, variesDueTo, leap years]
-
A.
varies
chosen
Indicates that the value, state, or condition of one entity changes in response to differences in another entity or context.
-
B.
usageVariesBy
Indicates that the way something is used differs depending on a specified factor, such as context, user, location, or conditions.
-
C.
variesOver
Indicates that the value, state, or behavior of one entity changes as a function of another entity or parameter.
-
D.
attributeVariesBy
Indicates that a particular attribute can take on different values depending on another variable, context, or condition.
-
E.
rateVariesBy
Indicates that the rate of something changes depending on a specified factor, condition, or category.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaa34e9c81909d42a85ba04f7c20 |
completed | May 3, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:07 p.m.