Triple
T7316881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brenda Leigh Johnson |
E168435
|
entity |
| Predicate | investigativeStyle |
P76266
|
FINISHED |
| Object | unorthodox |
—
|
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: unorthodox | Statement: [Brenda Leigh Johnson, investigativeStyle, unorthodox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: investigativeStyle Context triple: [Brenda Leigh Johnson, investigativeStyle, unorthodox]
-
A.
investigativeFocus
Indicates that an entity is the primary subject or target of investigation, inquiry, or detailed scrutiny by another entity.
-
B.
usesInvestigativeMethods
Indicates that an entity employs investigative techniques or procedures to gather information, analyze evidence, or uncover facts.
-
C.
investigatedBy
Indicates that an entity is the subject of an investigation carried out by another entity.
-
D.
investigatedUsing
Indicates that an investigation, study, or analysis was carried out by means of a specified method, tool, or resource.
-
E.
investigatedFor
Indicates that an entity is the subject of an investigation concerning a suspected involvement in another entity (typically a crime, incident, or wrongdoing).
- 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_69c68a5251508190ad68df4151cfeb04 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ef162d488190bf1c63b71b20a294 |
completed | March 27, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb88a2648190acc79eeee8733705 |
completed | March 27, 2026, 8:41 p.m. |
Created at: March 27, 2026, 3:02 p.m.