Triple
T11086063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proper of the Season |
E262122
|
entity |
| Predicate | isVariableWith |
P38220
|
FINISHED |
| Object | date of Easter |
—
|
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: date of Easter | Statement: [Proper of the Season, isVariableWith, date of Easter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVariableWith Context triple: [Proper of the Season, isVariableWith, date of Easter]
-
A.
hasVariable
chosen
Indicates that one entity includes, defines, or is associated with a particular variable.
-
B.
isVariableStar
Indicates that an astronomical object exhibits intrinsic brightness variations over time, classifying it as a variable star.
-
C.
hasVarianceSymbol
Indicates that one entity is associated with, or represented by, a specific variance symbol in a mathematical or statistical context.
-
D.
hasVariability
Indicates that an entity exhibits variation or fluctuation in its state, value, or characteristics over time or across instances.
-
E.
hasDependentVariable
Indicates that one variable’s value is determined by, or functionally depends on, the value(s) of another variable or set of variables.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799c3ed9c8190a3f5cdf1fe0e74a2 |
completed | April 9, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.