Triple
T17114542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euramerica |
E415305
|
entity |
| Predicate | hasApproximateTimeSpan |
P115721
|
FINISHED |
| Object | from late Silurian to early Permian |
—
|
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: from late Silurian to early Permian | Statement: [Euramerica, hasApproximateTimeSpan, from late Silurian to early Permian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateTimeSpan Context triple: [Euramerica, hasApproximateTimeSpan, from late Silurian to early Permian]
-
A.
hasApproximateDuration
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
B.
timePeriodApproximation
chosen
Indicates that the associated time period is an estimate or approximation rather than an exact, precise value.
-
C.
timeSpanIncludes
Indicates that one time span fully contains or covers the entire duration of another time span.
-
D.
hasApproximateEnd
Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
-
E.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e803ff848190b884fd2c3cc0ee48 |
completed | April 18, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.