Triple
T7316907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brenda Leigh Johnson |
E168435
|
entity |
| Predicate | commandPosition |
P19105
|
FINISHED |
| Object | supervises Major Crimes detectives |
—
|
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: supervises Major Crimes detectives | Statement: [Brenda Leigh Johnson, commandPosition, supervises Major Crimes detectives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandPosition Context triple: [Brenda Leigh Johnson, commandPosition, supervises Major Crimes detectives]
-
A.
commandOf
chosen
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
classPosition
Indicates the relative ordering or rank of an entity within a class, group, or sequence.
-
D.
positionCoached
Indicates that one entity served as a coach for another entity in a specific position or role.
-
E.
positionHead
Indicates that one entity serves as the head or primary governing element in the positional or syntactic structure of 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_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. |
Created at: March 27, 2026, 3:02 p.m.