Triple
T9956872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Assyrian Laws |
E195465
|
entity |
| Predicate | notableClause |
P7906
|
FINISHED |
| Object | laws on veiling of women |
—
|
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: laws on veiling of women | Statement: [Middle Assyrian Laws, notableClause, laws on veiling of women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableClause Context triple: [Middle Assyrian Laws, notableClause, laws on veiling of women]
-
A.
notableProvision
chosen
Indicates that one entity is a significant or noteworthy clause, term, or condition contained within another entity, such as a document, agreement, or law.
-
B.
notableCondition
Indicates that an entity has a medically or contextually significant condition associated with it.
-
C.
notableRule
Indicates that a rule or regulation is particularly significant, prominent, or noteworthy within a given context.
-
D.
notableProposition
Indicates that a subject is associated with a proposition, statement, or claim that is considered notable or significant in some context.
-
E.
notableAccord
Indicates a significant formal agreement, treaty, or understanding established between entities.
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6976b50819097a0ae347354e92c |
completed | April 2, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:46 p.m.