Triple
T19070566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metageitnion |
E466778
|
entity |
| Predicate | approximateGregorianRange |
P877
|
FINISHED |
| Object | July–August |
—
|
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: July–August | Statement: [Metageitnion, approximateGregorianRange, July–August]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateGregorianRange Context triple: [Metageitnion, approximateGregorianRange, July–August]
-
A.
hasApproxGregorianStart
Indicates that an entity has an associated start date expressed as an approximate value in the Gregorian calendar.
-
B.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
C.
chronologicallyBetween
Indicates that one event or time point occurs after a first reference point and before a second reference point in temporal order.
-
D.
dateRelativeToGregorian
Indicates how a given date is positioned or expressed in relation to the standard Gregorian calendar date.
-
E.
approximateEndCenturyBCE_CE
Indicates that an event or entity is estimated to have ended in a particular century, which may be expressed in either BCE or CE.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e19ea01c8190b9bb789da32f9a90 |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.