Triple
T28808546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Code of Hammurabi stele |
E727445
|
entity |
| Predicate | discoveredInPresentDay |
P16041
|
FINISHED |
| Object | Iran |
—
|
NE NERFINISHED |
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: Iran | Statement: [Code of Hammurabi stele, discoveredInPresentDay, Iran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredInPresentDay Context triple: [Code of Hammurabi stele, discoveredInPresentDay, Iran]
-
A.
wasDiscoveredIn
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
-
B.
isLocatedInPresentDayCountry
Indicates that an entity’s location is specified in terms of the modern, currently recognized country that encompasses it.
-
C.
discoveredInCountry
chosen
Indicates that something was discovered within the geographical boundaries or jurisdiction of a specified country.
-
D.
tookPlaceInPresentDayCountry
Indicates that an event or occurrence happened within the geographic area of the country as it is defined in the present day.
-
E.
usedInPresentDayCountry
Indicates that something is currently utilized or occurs within the boundaries of a specified modern-day country.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 28, 2026, 6:30 a.m.