Triple
T4358318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Variscan orogeny |
E98603
|
entity |
| Predicate | timeSpanApproximate |
P302
|
FINISHED |
| Object | about 400 to 280 million years ago |
—
|
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: about 400 to 280 million years ago | Statement: [Variscan orogeny, timeSpanApproximate, about 400 to 280 million years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSpanApproximate Context triple: [Variscan orogeny, timeSpanApproximate, about 400 to 280 million years ago]
-
A.
timeStartApprox
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
B.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
D.
hasApproximateDuration
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
E.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351c7fa1881908bdc844a7142eb65 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:16 p.m.