Triple
T30743614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Line site |
E782757
|
entity |
| Predicate | chronologicalDesignation |
P18401
|
FINISHED |
| Object | Late Prehistoric |
—
|
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: Late Prehistoric | Statement: [State Line site, chronologicalDesignation, Late Prehistoric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalDesignation Context triple: [State Line site, chronologicalDesignation, Late Prehistoric]
-
A.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
B.
chronologyType
Indicates the type or system of chronological ordering or dating applied to an event, period, or sequence.
-
C.
chronologicalPoint
Indicates that something is associated with, occurs at, or is anchored to a specific point in time within a chronological sequence.
-
D.
chronologicRank
Indicates the relative position or order of something within a sequence based on time.
-
E.
chronologicallyClassifiedAs
chosen
Indicates that something is assigned to or placed within a specific time period or chronological category.
- 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_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 29, 2026, 8:38 p.m.