Triple
T30868710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clovis-first debate |
E786275
|
entity |
| Predicate | concernsDateRange |
P146610
|
FINISHED |
| Object | approximately 13,000 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: approximately 13,000 years ago | Statement: [Clovis-first debate, concernsDateRange, approximately 13,000 years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsDateRange Context triple: [Clovis-first debate, concernsDateRange, approximately 13,000 years ago]
-
A.
concernsDate
Indicates that something is related or refers specifically to a particular date or point in time.
-
B.
occurredBetween
Indicates that an event or action took place within the time interval defined by two temporal boundaries.
-
C.
createdBetween
Indicates that something was created within a specified start and end time or date range.
-
D.
chronologicallyBetween
Indicates that one event or time point occurs after a first reference point and before a second reference point in temporal order.
-
E.
concernsPeriod
chosen
Indicates that something is related or applicable to a specific time period or span of time.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 29, 2026, 8:47 p.m.