Triple
T26309149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army of Difficulty |
E661770
|
entity |
| Predicate | timePeriodGregorianApprox |
P163453
|
FINISHED |
| Object | 630 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: 630 CE | Statement: [Army of Difficulty, timePeriodGregorianApprox, 630 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodGregorianApprox Context triple: [Army of Difficulty, timePeriodGregorianApprox, 630 CE]
-
A.
timePeriodApproximation
Indicates that the associated time period is an estimate or approximation rather than an exact, precise value.
-
B.
dateRelativeToGregorian
Indicates how a given date is positioned or expressed in relation to the standard Gregorian calendar date.
-
C.
accuracyComparedToTropicalYear
Indicates how closely something’s measured or defined duration matches the length of a tropical year.
-
D.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
E.
occursInGregorianPeriod
chosen
Indicates that an event or occurrence takes place within a specified time interval defined in the Gregorian calendar.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 26, 2026, 10:21 p.m.