Triple
T6274525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Province of Lichfield |
E140622
|
entity |
| Predicate | apexTime |
P69103
|
FINISHED |
| Object | late 8th 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: late 8th century | Statement: [Province of Lichfield, apexTime, late 8th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apexTime Context triple: [Province of Lichfield, apexTime, late 8th century]
-
A.
apexOf
Indicates that one entity is the highest or most extreme point, level, or culmination of another entity or process.
-
B.
apexOriginallyCappedBy
Indicates that the topmost point or peak of something was initially covered, sealed, or finished with a particular cap or crowning element.
-
C.
endTimeAsCapital
Indicates that a specified time marks the ending point of an event, process, or state in the role of its designated capital or primary endpoint.
-
D.
latestTime
Indicates the most recent point in time at which the related event, state, or condition occurs or is valid among a set of possible times.
-
E.
timeAfterAble
Indicates that one event, state, or action occurs after another point in time at which it becomes possible or permissible.
- 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_69c008cc158881908df6ec94a911c736 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063c0629c8190805ddf1a604e9ca4 |
completed | March 22, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69c05606fb50819082d1a5a91e5030b6 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c965ac8190b938502fa8c74e1b |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:25 p.m.