Triple
T23290426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judgment Calls |
E590011
|
entity |
| Predicate | hasAuthorProfessionBackground |
P72668
|
FINISHED |
| Object | former prosecutor |
—
|
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: former prosecutor | Statement: [Judgment Calls, hasAuthorProfessionBackground, former prosecutor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorProfessionBackground Context triple: [Judgment Calls, hasAuthorProfessionBackground, former prosecutor]
-
A.
hasAuthorialBackground
Indicates that an entity has a creator or author with a specific background, context, or set of characteristics associated with them.
-
B.
hasAuthorBackgroundIn
chosen
Indicates that an author possesses a particular background, such as education, experience, or expertise, in a specified field or domain.
-
C.
hasAuthorOccupationOfAuthor
Indicates that an author has a specific occupation or professional role.
-
D.
hasCoauthorBackground
Indicates that two or more coauthors share a specified background, such as educational, professional, cultural, or experiential context.
-
E.
hasGivenProfession
Indicates that an entity holds or practices a specified profession or occupation.
- 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_69e25d1af9d88190a0b9b5e8fa608618 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1964a4c548190bda1e85b8d316e8a |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:01 p.m.