Triple
T2801006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moravian Daily Texts |
E53152
|
entity |
| Predicate | hasTemporalStructure |
P25625
|
FINISHED |
| Object | one reading for each calendar day |
—
|
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: one reading for each calendar day | Statement: [Moravian Daily Texts, hasTemporalStructure, one reading for each calendar day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTemporalStructure Context triple: [Moravian Daily Texts, hasTemporalStructure, one reading for each calendar day]
-
A.
hasTemporalLocation
Indicates that something occurs, exists, or is valid during a specific time or time interval.
-
B.
temporalAspect
Indicates the time-related characteristics or phase (such as duration, frequency, or temporal status) associated with an event or relationship.
-
C.
temporalRelation
Indicates a relationship that specifies how two events or states are positioned relative to each other in time (e.g., before, after, or overlapping).
-
D.
timeStructure
chosen
Indicates that one entity defines, constrains, or organizes the temporal framework or schedule within which another entity exists or operates.
-
E.
hasTimeDepth
Indicates that something possesses or spans a measurable extent of time, such as duration, historical depth, or temporal layering.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abde2ec2ac8190bd702ad3eafb6aed |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd059f308190853191f6ffe2bc6f |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.