Triple
T1900946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Code of Hammurabi |
E37686
|
entity |
| Predicate | containsEpilogue |
P9713
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Code of Hammurabi, containsEpilogue, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsEpilogue Context triple: [Code of Hammurabi, containsEpilogue, yes]
-
A.
includesSpokenEpilogue
chosen
Indicates that the work contains a spoken epilogue segment delivered after the main content concludes.
-
B.
isFinalChapterOf
Indicates that one entity is the concluding or last chapter within the sequence of chapters of another entity (typically a work or volume).
-
C.
endedWith
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
D.
hasTragicEnding
Indicates that the event, story, or situation concludes with a sorrowful, disastrous, or otherwise deeply unfortunate outcome.
-
E.
hasEP
Indicates that an entity possesses, is associated with, or is characterized by a specific EP (e.g., an endpoint, event point, or designated EP resource) in the given context.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafe9f8b0819086d8f6288511c66d |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.