Triple
T19675957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menoceras |
E472452
|
entity |
| Predicate | temporalRangeApproximate |
P115721
|
FINISHED |
| Object | about 23 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 23 million years ago | Statement: [Menoceras, temporalRangeApproximate, about 23 million years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalRangeApproximate Context triple: [Menoceras, temporalRangeApproximate, about 23 million years ago]
-
A.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
B.
timePeriodApproximation
chosen
Indicates that the associated time period is an estimate or approximation rather than an exact, precise value.
-
C.
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.
-
D.
timeframeApproximate
Indicates that the time period associated with an event or relation is not exact but only roughly or loosely specified.
-
E.
collectionTimespan
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641bbea8c8190b0ad841d95068e0e |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e514eb37b8819091502cc954f70eba |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.