Triple
T32731113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gerzeh |
E836956
|
entity |
| Predicate | ironBeadsDating |
P116053
|
FINISHED |
| Object | before widespread smelted iron technology in Egypt |
—
|
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: before widespread smelted iron technology in Egypt | Statement: [Gerzeh, ironBeadsDating, before widespread smelted iron technology in Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ironBeadsDating Context triple: [Gerzeh, ironBeadsDating, before widespread smelted iron technology in Egypt]
-
A.
ironBeadsMaterial
Indicates that the material composition of the beads is iron.
-
B.
tombDating
Indicates a relationship specifying the estimated or known time period during which a tomb was constructed, used, or relevant.
-
C.
scientificDating
chosen
Indicates that an object or material has been assigned an age or time period using scientific dating methods (e.g., radiocarbon, dendrochronology, or other analytical techniques).
-
D.
yearOfIsotopeIdentification
Indicates the year in which a particular isotope was first identified or discovered.
-
E.
inscriptionDating
Indicates the temporal period or specific date to which an inscription is assigned or attributed.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:11 a.m.