Triple
T15460424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acheroraptor temertyorum |
E371883
|
entity |
| Predicate | moreSpecificTemporalRange |
P97853
|
FINISHED |
| Object | Maastrichtian |
—
|
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: Maastrichtian | Statement: [Acheroraptor temertyorum, moreSpecificTemporalRange, Maastrichtian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moreSpecificTemporalRange Context triple: [Acheroraptor temertyorum, moreSpecificTemporalRange, Maastrichtian]
-
A.
temporal scope
Indicates the time period or duration over which a particular relationship, condition, or fact holds true.
-
B.
hasTemporalResolution
Indicates that one entity specifies the level of temporal detail or granularity at which another entity’s data, observation, or process is measured or represented.
-
C.
morePreciseDate
chosen
Indicates that one date value specifies a more detailed or exact point in time than another related date value.
-
D.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
E.
timePeriodOfRefinement
Indicates the specific time span during which a refinement or improvement of something takes place.
- 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_69e03f17663c8190b995c7c3129c90d6 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:32 a.m.