Triple
T28535601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanigalbat |
E722153
|
entity |
| Predicate | usedInSourceType |
P182837
|
FINISHED |
| Object | Assyrian royal inscriptions |
—
|
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: Assyrian royal inscriptions | Statement: [Hanigalbat, usedInSourceType, Assyrian royal inscriptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInSourceType Context triple: [Hanigalbat, usedInSourceType, Assyrian royal inscriptions]
-
A.
usedAsSourceIn
Indicates that something serves as the origin, basis, or input from which another thing is derived, produced, or obtained.
-
B.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
C.
usesSourceType
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
-
D.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
E.
mentionedInSourceType
Indicates that something is referenced or cited within a source of a particular type (e.g., book, article, website).
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f794f24e588190965e39b77534d53f |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: April 28, 2026, 3:31 a.m.