Triple
T30588574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isin-Larsa period |
E778584
|
entity |
| Predicate | hasLegalDevelopment |
P191358
|
FINISHED |
| Object | Lipit-Ishtar law code |
—
|
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: Lipit-Ishtar law code | Statement: [Isin-Larsa period, hasLegalDevelopment, Lipit-Ishtar law code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalDevelopment Context triple: [Isin-Larsa period, hasLegalDevelopment, Lipit-Ishtar law code]
-
A.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
B.
hasLegalRight
Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding another entity.
-
C.
hasLegalPosition
Indicates that an entity holds a specific legal role, status, or standing within a legal framework or proceeding.
-
D.
hasLegalResponse
Indicates that an entity has an associated legal reply, action, or measure taken in response to a legal situation, claim, or requirement.
-
E.
legalIn
Indicates that an action, status, or entity is permitted or valid under the laws or regulations of a specified jurisdiction.
- F. None of above. chosen
Provenance (4 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: April 29, 2026, 8:24 p.m.