Triple
T33047470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laonikos Chalkokondyles |
E845633
|
entity |
| Predicate | chronologicalRangeOfWork |
P82593
|
FINISHED |
| Object | 1298–1463 |
—
|
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: 1298–1463 | Statement: [Laonikos Chalkokondyles, chronologicalRangeOfWork, 1298–1463]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalRangeOfWork Context triple: [Laonikos Chalkokondyles, chronologicalRangeOfWork, 1298–1463]
-
A.
chronologicalRange
chosen
Indicates the temporal span or period over which something occurs, is valid, or is relevant.
-
B.
chronologicalRangeOfNotes
Indicates the time span or period covered by the associated notes in chronological order.
-
C.
chronologyEndWork
Indicates that a work marks the end point or final item in a chronological sequence or timeline.
-
D.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
-
E.
notableWorkPeriod
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 1, 2026, 1:24 a.m.