Triple
T14740492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beatrix of Świdnica |
E346330
|
entity |
| Predicate | chronological context |
P89854
|
FINISHED |
| Object | 14th century |
—
|
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: 14th century | Statement: [Beatrix of Świdnica, chronological context, 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronological context Context triple: [Beatrix of Świdnica, chronological context, 14th century]
-
A.
chronologicalSignificance
Indicates that one entity holds importance or relevance specifically due to its position, order, or timing within a chronological sequence relative to another.
-
B.
chronologicalEffect
Indicates that one event or state occurs as a temporal consequence of, or in sequence after, another.
-
C.
chronologicalPoint
chosen
Indicates that something is associated with, occurs at, or is anchored to a specific point in time within a chronological sequence.
-
D.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
-
E.
chronologyNote
Indicates a note that explains or clarifies the temporal order, dating, or sequence of related events or records.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7345680819093e901233a064e48 |
completed | April 14, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.