Triple
T36663569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquitanian Stage |
E905197
|
entity |
| Predicate | lowerBoundaryGSSPYear |
P90270
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Aquitanian Stage, lowerBoundaryGSSPYear, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerBoundaryGSSPYear Context triple: [Aquitanian Stage, lowerBoundaryGSSPYear, 1996]
-
A.
lowerBoundaryGSSPApprovedBy
Indicates that the formal Global Boundary Stratotype Section and Point (GSSP) defining the lower boundary of a geologic stage or unit has been officially approved by a specified authority or body.
-
B.
knownLowerBoundYear
chosen
Indicates that the associated year value is the earliest known or confirmed lower bound in time for the related event or state.
-
C.
lowerBoundaryLocation
Indicates the place or region where the lower or bottom boundary of something is situated.
-
D.
earliestStrataDate
Indicates the earliest known or recorded date associated with a particular geological or archaeological stratum.
-
E.
lastGlacialMaximumApproximate
Indicates that the subject time or event occurs approximately during the period of the Last Glacial Maximum.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:12 p.m.