Triple
T30744443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Folsom culture |
E782779
|
entity |
| Predicate | chronologicallyLaterThan |
P6880
|
FINISHED |
| Object | Clovis culture |
—
|
NE NERFINISHED |
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: Clovis culture | Statement: [Folsom culture, chronologicallyLaterThan, Clovis culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicallyLaterThan Context triple: [Folsom culture, chronologicallyLaterThan, Clovis culture]
-
A.
chronologicallyAfter
chosen
Indicates that one event or state occurs later in time than another.
-
B.
notEarlierThan
Indicates that one event, time, or state does not occur before another, i.e., it is simultaneous with or later than the referenced point.
-
C.
chronologicallyBetween
Indicates that one event or time point occurs after a first reference point and before a second reference point in temporal order.
-
D.
isNewerThan
Indicates that one entity has a more recent creation, modification, or occurrence time compared to another entity.
-
E.
arisesAfter
Indicates that one event, state, or condition comes into existence or begins only after another specified event, state, or condition has occurred.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 29, 2026, 8:38 p.m.