Triple
T19784235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amasa |
E475216
|
entity |
| Predicate | appointmentContext |
P137313
|
FINISHED |
| Object | Absalom's rebellion against David |
—
|
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: Absalom's rebellion against David | Statement: [Amasa, appointmentContext, Absalom's rebellion against David]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointmentContext Context triple: [Amasa, appointmentContext, Absalom's rebellion against David]
-
A.
appointmentBody
Indicates that one entity serves as the main content or body text associated with a particular appointment.
-
B.
appointmentBy
Indicates that one entity is appointed or designated to a role, position, or task by another entity.
-
C.
appointmentTerm
Indicates the duration or specific period for which an appointment, position, or role is held.
-
D.
appointmentType
Indicates the specific category or nature of an appointment associated with an entity or event.
-
E.
appointmentsInvolve
Indicates that scheduled appointments include or engage specific participants, resources, or activities in the appointment event.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65385ee8081908d58cc3ff05b9b23 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:49 p.m.