Triple
T29143015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samuel Norton |
E738686
|
entity |
| Predicate | keepsItem |
P95282
|
FINISHED |
| Object | Bible with hidden rock hammer compartment |
—
|
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: Bible with hidden rock hammer compartment | Statement: [Samuel Norton, keepsItem, Bible with hidden rock hammer compartment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keepsItem Context triple: [Samuel Norton, keepsItem, Bible with hidden rock hammer compartment]
-
A.
keptIn
Indicates that one entity is stored, contained, or maintained inside another entity as its location or container.
-
B.
isKeptBy
chosen
Indicates that something is maintained, possessed, or held in the care or custody of a particular entity.
-
C.
keptWith
Indicates that one entity is stored, maintained, or held together in association with another entity.
-
D.
isKeptFor
Indicates that one entity is retained or preserved for the benefit, use, or purpose of another entity.
-
E.
isKeptAs
Indicates that one entity is maintained, preserved, or retained by another entity, often implying possession, storage, or ongoing custody.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f662707bfc819093d188364a088311 |
completed | May 2, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:37 a.m.