Triple
T28137500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuriev Day peasant departure rule |
E714249
|
entity |
| Predicate | departureWindow |
P164065
|
FINISHED |
| Object | narrow annual period |
—
|
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: narrow annual period | Statement: [Yuriev Day peasant departure rule, departureWindow, narrow annual period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: departureWindow Context triple: [Yuriev Day peasant departure rule, departureWindow, narrow annual period]
-
A.
departureTime
Indicates the specific time at which an entity leaves or begins its departure from a location or state.
-
B.
hasDepartureEnd
Indicates that an entity marks the endpoint or final location of a departure event or journey.
-
C.
departureFromTargetDate
Indicates the difference between an actual departure date and a specified target departure date.
-
D.
hasDepartureTo
Indicates that a departure event originates from one place and is directed toward a specific destination.
-
E.
departureYear
Indicates the calendar year in which an entity leaves, exits, or ceases its association with another entity or location.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 9:51 p.m.