Triple
T35913260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | summer solstice |
E1038678
|
entity |
| Predicate | oppositeEvent |
P34818
|
FINISHED |
| Object | winter solstice |
—
|
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: winter solstice | Statement: [summer solstice, oppositeEvent, winter solstice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppositeEvent Context triple: [summer solstice, oppositeEvent, winter solstice]
-
A.
opposite
chosen
Indicates that one entity is positioned or oriented directly across from, or in a contrary or reverse relation to, another entity.
-
B.
alternativeEvent
Indicates that one event serves as an alternative or substitute option to another event within the same context.
-
C.
opposedOperation
Indicates that one operation is in conflict with, counters, or works against another operation.
-
D.
opposedDuring
Indicates that one entity actively resisted or was in conflict with another entity during a specified time period or event.
-
E.
oppositeFacility
Indicates that one facility is located directly across from or facing another facility.
- 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_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 3, 2026, 4:07 p.m.