Triple
T26535429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mound RGR-7 |
E671230
|
entity |
| Predicate | chronologicalAttribution |
P89854
|
FINISHED |
| Object | Bronze Age |
—
|
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: Bronze Age | Statement: [Mound RGR-7, chronologicalAttribution, Bronze Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalAttribution Context triple: [Mound RGR-7, chronologicalAttribution, Bronze Age]
-
A.
chronologicalSignificance
Indicates that one entity holds importance or relevance specifically due to its position, order, or timing within a chronological sequence relative to another.
-
B.
chronologicalPoint
chosen
Indicates that something is associated with, occurs at, or is anchored to a specific point in time within a chronological sequence.
-
C.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
D.
chronologicalUncertainty
Indicates that the timing or chronological order of an event or relationship is uncertain or not precisely known.
-
E.
chronologyCertainty
Indicates the degree of confidence or uncertainty about the ordering or dating of events or temporal relationships.
- 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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 1:38 a.m.