Triple
T12432979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Johnson |
E297076
|
entity |
| Predicate | isAttorney |
P5610
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mike Johnson, isAttorney, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAttorney Context triple: [Mike Johnson, isAttorney, true]
-
A.
legalProfessionIncludes
Indicates that a legal profession or role encompasses, involves, or includes another specified legal function, specialization, or activity.
-
B.
legalProfessionRole
chosen
Indicates that one entity holds or performs a specific professional role within the legal domain in relation to another entity or context.
-
C.
hasCounsel
Indicates that one entity serves as a legal advisor or representative (counsel) for another entity.
-
D.
allowsRepresentationByLawyers
Indicates that one party permits or recognizes the right of another party to be represented by lawyers in a given context or proceeding.
-
E.
isSeniorLegalOfficerFor
Indicates that one person holds a senior legal authority or leadership role with primary legal responsibility for another entity (such as an organization, unit, or individual).
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.