Triple
T6906976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lambityeco |
E159836
|
entity |
| Predicate | approximatePeakDate |
P877
|
FINISHED |
| Object | 600–800 CE |
—
|
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: 600–800 CE | Statement: [Lambityeco, approximatePeakDate, 600–800 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximatePeakDate Context triple: [Lambityeco, approximatePeakDate, 600–800 CE]
-
A.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
B.
peakRatingDate
Indicates the date on which an entity reached its highest (peak) rating within a given rating history or period.
-
C.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
D.
latestPossibleDate
Indicates the most recent date on which a given event, condition, or state can validly or feasibly occur.
-
E.
peakApproximateMa
Indicates that one entity’s peak value is approximately equal to another entity’s peak value.
- 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d98c3ab08190a1830c45578056ac |
completed | March 27, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:25 p.m.