Triple
T9171003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nephites |
E220078
|
entity |
| Predicate | keptRecordsOn |
P35371
|
FINISHED |
| Object | metal 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: metal plates | Statement: [Nephites, keptRecordsOn, metal plates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keptRecordsOn Context triple: [Nephites, keptRecordsOn, metal 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.
keptIn
chosen
Indicates that one entity is stored, contained, or maintained inside another entity as its location or container.
-
C.
statusRecordedBy
Indicates that the status of an entity was documented or captured by a specific agent or system.
-
D.
poweredRecord
Indicates that one entity functions as a powered or electrified version of another entity, typically enabling enhanced or active operation.
-
E.
isRememberedOn
Indicates that an entity is commemorated, recalled, or honored on a specific date or occasion.
- 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaae38ee48190bf783477bc37913d |
completed | April 1, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:22 p.m.