Triple
T30875946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omni |
E786475
|
entity |
| Predicate | recordsKeptOn |
P2722
|
FINISHED |
| Object | small plates of Nephi |
—
|
NE NERFINISHED |
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: small plates of Nephi | Statement: [Omni, recordsKeptOn, small plates of Nephi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordsKeptOn Context triple: [Omni, recordsKeptOn, small plates of Nephi]
-
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.
recordKeepingSystem
Indicates a relationship where an entity functions as or is associated with a system used to store, manage, and maintain records or information.
-
C.
recordsWith
Indicates that one entity keeps or maintains documented information about another entity or event.
-
D.
recordHeldIn
Indicates that a record is stored, maintained, or kept within a particular location, system, or repository.
-
E.
recordHeld
chosen
Indicates that one entity possesses or maintains a particular record associated with another entity or 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 29, 2026, 8:48 p.m.