Triple
T34481378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimaatre |
E885193
|
entity |
| Predicate | chronologicalApproximation |
P162912
|
FINISHED |
| Object | 19th century BCE |
—
|
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: 19th century BCE | Statement: [Nimaatre, chronologicalApproximation, 19th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalApproximation Context triple: [Nimaatre, chronologicalApproximation, 19th century BCE]
-
A.
chronologicalUncertainty
Indicates that the timing or chronological order of an event or relationship is uncertain or not precisely known.
-
B.
chronologicalPeriodApprox
chosen
Indicates that one entity is associated with a time period that is approximately, but not exactly, the same as the time period of another entity.
-
C.
chronologyCertainty
Indicates the degree of confidence or uncertainty about the ordering or dating of events or temporal relationships.
-
D.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
-
E.
relativeChronology
Indicates a temporal ordering relationship that specifies how one event or state is positioned in time relative to another (e.g., earlier, later, or overlapping).
- 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_69f349c947fc81909d30b53c194d6ea1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 1, 2026, 2:01 a.m.