Triple
T32656305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toarcis |
E834869
|
entity |
| Predicate | associatedTimeInterval |
P123510
|
FINISHED |
| Object | Early Jurassic |
—
|
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: Early Jurassic | Statement: [Toarcis, associatedTimeInterval, Early Jurassic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedTimeInterval Context triple: [Toarcis, associatedTimeInterval, Early Jurassic]
-
A.
associatedWithTime
Indicates a relationship where something is linked or connected to a specific point or period in time.
-
B.
originalTimeInterval
Indicates the initial or primary time span during which an event, state, or relationship is considered to occur, before any adjustments or derived intervals.
-
C.
timeIntervalLength
Indicates the duration or length of a specified time interval.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
timePeriodAttributed
chosen
Indicates that a specific time period is assigned or associated with an entity as its relevant temporal context.
- 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:08 a.m.