Triple
T9400052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaredites |
E226443
|
entity |
| Predicate | recordKeptOn |
P2722
|
FINISHED |
| Object | 24 gold plates |
—
|
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: 24 gold plates | Statement: [Jaredites, recordKeptOn, 24 gold plates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordKeptOn Context triple: [Jaredites, recordKeptOn, 24 gold plates]
-
A.
recordKeeper
Indicates a relationship where one entity is responsible for maintaining, managing, or preserving official records or documented information about another entity or activity.
-
B.
recordHeld
chosen
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
-
C.
recordHeldIn
Indicates that a record is stored, maintained, or kept within a particular location, system, or repository.
-
D.
keptIn
Indicates that one entity is stored, contained, or maintained inside another entity as its location or container.
-
E.
recordHeldFor
Indicates that one entity is being kept, stored, or maintained on behalf of or in relation to another entity.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5156b9588190bafb6b1c3ee3c0ed |
completed | April 1, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:46 p.m.