Triple
T28654217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moses Blah |
E725283
|
entity |
| Predicate | laterTestifiedAgainst |
P81793
|
FINISHED |
| Object | Charles Taylor |
—
|
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: Charles Taylor | Statement: [Moses Blah, laterTestifiedAgainst, Charles Taylor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterTestifiedAgainst Context triple: [Moses Blah, laterTestifiedAgainst, Charles Taylor]
-
A.
soughtTestimonyAgainst
Indicates that one party actively attempted to obtain another party’s testimony to be used against a specified target in a legal or investigative context.
-
B.
gaveTestimonyIn
Indicates that one entity provided formal testimony or a statement in an official proceeding, event, or context associated with another entity.
-
C.
testimonyAffects
chosen
Indicates that one party’s testimony has an influence or impact on another entity, situation, or outcome.
-
D.
hasTestimony
Indicates that an entity provides, contains, or is associated with a formal statement or account (testimony) about another entity or event.
-
E.
ledAgainst
Indicates that one entity directed or commanded an opposing effort, campaign, or force against another entity.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: April 28, 2026, 4:54 a.m.