Triple
T15454537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Germinal |
E371734
|
entity |
| Predicate | typicalStartGregorianRange |
P58421
|
FINISHED |
| Object | around March 21 |
—
|
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: around March 21 | Statement: [Germinal, typicalStartGregorianRange, around March 21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStartGregorianRange Context triple: [Germinal, typicalStartGregorianRange, around March 21]
-
A.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
B.
hasApproxGregorianStart
Indicates that an entity has an associated start date expressed as an approximate value in the Gregorian calendar.
-
C.
typicalEndDateRange
Indicates the usual or expected range of end dates associated with an event, activity, or time-bounded entity.
-
D.
typicalStartTimeOfYear
chosen
Indicates the usual or characteristic time of year when something typically begins or occurs.
-
E.
startYearOfCommonObservance
Indicates the year in which a particular observance, practice, or recognition began to be commonly or widely observed.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f131b1481909ff099c3b844ee07 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:31 a.m.