Triple
T218863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Nights |
E4169
|
entity |
| Predicate | occursNear |
P8203
|
FINISHED |
| Object | summer 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: summer solstice | Statement: [White Nights, occursNear, summer solstice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursNear Context triple: [White Nights, occursNear, summer solstice]
-
A.
near
Indicates that one entity is located at a short distance from another entity in space or position.
-
B.
isAdjacentTo
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
C.
passesNearCity
Indicates that the path, route, or trajectory of one entity goes close to, but not necessarily through, a specified city.
-
D.
locatedAfter
Indicates that one entity is positioned later than another along a defined sequence, order, or spatial/temporal axis.
-
E.
locatedBetween
Indicates that one entity is positioned spatially between two other reference entities.
- F. None of above. chosen
Provenance (4 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c5199d8819096736c11077adec3 |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5357bc8190b29a48e3053fb76d |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25be349588190aedde33d80682344 |
completed | Feb. 28, 2026, 3:07 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.