Triple
T36596964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perfects |
E902827
|
entity |
| Predicate | historicalEnd |
P39746
|
FINISHED |
| Object | largely eradicated by late 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: largely eradicated by late 14th century | Statement: [Perfects, historicalEnd, largely eradicated by late 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEnd Context triple: [Perfects, historicalEnd, largely eradicated by late 14th century]
-
A.
chronologyEnd
Indicates that one event, state, or time interval marks the ending point or conclusion of another in a temporal sequence.
-
B.
periodDepictedEnd
Indicates the time period or date at which the depicted event, scene, or situation comes to an end.
-
C.
chronologicalCoverageEnd
Indicates the point in time at which the temporal or chronological span of something (such as a resource, event, or record) comes to an end.
-
D.
historicalTerminus
chosen
Indicates that one entity serves as the historically recognized endpoint or final limit of another entity, such as a route, period, or process.
-
E.
chroniclesEndDate
Indicates the date on which a chronicle, record, or documented series of events concludes.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a013c50bcb8819086d163f1a796a9b8 |
completed | May 11, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_6a013c01bac88190b15c70910c02a8a7 |
completed | May 11, 2026, 2:16 a.m. |
Created at: May 3, 2026, 4:11 p.m.