Triple
T8068853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunrise |
E188315
|
entity |
| Predicate | accessRestrictedInWinter |
P9584
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sunrise, accessRestrictedInWinter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessRestrictedInWinter Context triple: [Sunrise, accessRestrictedInWinter, true]
-
A.
accessRestrictedTo
Indicates that access to a resource, location, or information is limited exclusively to a specified entity or group under defined conditions.
-
B.
winterStatus
Indicates the condition, phase, or circumstances associated with the winter season for a given entity or context.
-
C.
accessRestriction
chosen
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
D.
requiresEquipmentInWinter
Indicates that performing the related activity or fulfilling the related condition necessitates the use of specific equipment during winter.
-
E.
hasWinterBreak
Indicates that an entity includes or provides a designated period of time off during the winter season.
- 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_69ca82b42674819086840efea12478e5 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ffbd59c8190a34398ddb4ee551e |
completed | March 31, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:27 p.m.