Triple
T31207683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the brother of Jared |
E795645
|
entity |
| Predicate | receivedCommandment |
P176764
|
FINISHED |
| Object | to gather his family and friends |
—
|
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: to gather his family and friends | Statement: [the brother of Jared, receivedCommandment, to gather his family and friends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedCommandment Context triple: [the brother of Jared, receivedCommandment, to gather his family and friends]
-
A.
containsCommandment
Indicates that one entity includes or encompasses a specific commandment as part of its content or structure.
-
B.
commandmentType
Indicates the specific category or kind of commandment that an instruction or directive belongs to.
-
C.
numberOfCommandments
Indicates the total count of commandments associated with a given subject.
-
D.
commandedIn
Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
-
E.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e60109648190947a64ca4ce81a3a |
completed | May 3, 2026, 6:06 a.m. |
Created at: April 29, 2026, 9:09 p.m.