Triple
T30740896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ammaron |
E782686
|
entity |
| Predicate | gaveChargeTo |
P170083
|
FINISHED |
| Object | Mormon |
—
|
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: Mormon | Statement: [Ammaron, gaveChargeTo, Mormon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gaveChargeTo Context triple: [Ammaron, gaveChargeTo, Mormon]
-
A.
chargesVia
Indicates that one entity charges or powers another entity using a specified medium, method, or interface.
-
B.
hasCharge
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
-
C.
chargedIn
Indicates that a legal charge or accusation against an entity was formally filed or brought in a particular jurisdiction, court, or case.
-
D.
chargeOnChief
Indicates that a formal accusation or legal charge is filed against a chief or primary authority figure.
-
E.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
- F. None of above. chosen
Provenance (4 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f68da34819092a2e476e5f6ee05 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f68848ad348190a2fb6e841dcfdb7d |
completed | May 2, 2026, 11:27 p.m. |
Created at: April 29, 2026, 8:38 p.m.