Triple
T30529970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shuruppak |
E776966
|
entity |
| Predicate | timeOfMajorFloodLayer |
P39938
|
FINISHED |
| Object | early 3rd millennium 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: early 3rd millennium BCE | Statement: [Shuruppak, timeOfMajorFloodLayer, early 3rd millennium BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfMajorFloodLayer Context triple: [Shuruppak, timeOfMajorFloodLayer, early 3rd millennium BCE]
-
A.
yearOfMajorFlooding
Indicates the specific year in which a major flooding event occurred for the associated entity.
-
B.
dateOfMajorDrainageEvent
Indicates the specific date on which a significant drainage-related event (such as major flooding, diversion, or alteration of water flow) occurred.
-
C.
floodRecord
Indicates that an entity serves as a documented record or report of a flood event affecting another entity or area.
-
D.
floodEvent
chosen
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
E.
timePeriodOfMajorDestruction
Indicates the time span during which a major destructive event affecting the subject 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 29, 2026, 8:18 p.m.