Triple
T13050777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilkiah |
E327441
|
entity |
| Predicate | sourceForBookDiscovery |
P10578
|
FINISHED |
| Object | 2 Kings 22 |
—
|
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: 2 Kings 22 | Statement: [Hilkiah, sourceForBookDiscovery, 2 Kings 22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceForBookDiscovery Context triple: [Hilkiah, sourceForBookDiscovery, 2 Kings 22]
-
A.
bookSelection
Indicates the act or result of choosing a particular book from a set of available options.
-
B.
bookMention
Indicates that one entity (such as a text, person, or source) makes reference to or cites a particular book.
-
C.
libraryCatalog
Indicates a relationship where a library’s catalog system organizes, indexes, and provides access information for the items held in the library’s collection.
-
D.
literarySource
chosen
Indicates that one entity serves as the written or literary origin, reference, or basis for another entity.
-
E.
soughtPassage
Indicates that one entity attempted to obtain or gain access to a particular passage, route, or way through something.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:57 p.m.