Triple
T38397585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sḫm-ḫt |
E900802
|
entity |
| Predicate | reignedInCenturyBC |
P137681
|
FINISHED |
| Object | 27th century BC |
—
|
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: 27th century BC | Statement: [Sḫm-ḫt, reignedInCenturyBC, 27th century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignedInCenturyBC Context triple: [Sḫm-ḫt, reignedInCenturyBC, 27th century BC]
-
A.
reignCenturyBCE
chosen
Indicates that a subject’s reign or rule occurred during a specified century before the Common Era (BCE).
-
B.
constructedInCenturyBCE
Indicates that something was built or created during a specified century before the Common Era (BCE).
-
C.
approximateBirthCenturyBCE
Indicates that an entity’s birth is estimated to have occurred within a specified century before the Common Era (BCE), rather than on an exact year or date.
-
D.
approximateCenturyBC
Indicates that something occurred or existed around a specified century before the start of the Common Era, with the time given as an approximate rather than exact century.
-
E.
eraStartYearBC
Indicates the year (counting backward from year 1) in which a particular era or period begins, expressed in the BC (Before Christ/BCE) dating system.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 3, 2026, 4:31 p.m.