Triple
T8800962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Will Hunting |
E209403
|
entity |
| Predicate | hasLegalIssues |
P4511
|
FINISHED |
| Object | history of assault charges |
—
|
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: history of assault charges | Statement: [Will Hunting, hasLegalIssues, history of assault charges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalIssues Context triple: [Will Hunting, hasLegalIssues, history of assault charges]
-
A.
hasLegalIssue
chosen
Indicates that an entity is involved in, associated with, or subject to a legal problem, dispute, or proceeding.
-
B.
hasLegalProceeding
Indicates that there is a formal legal action, case, or proceeding involving the related entities.
-
C.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
D.
legalMatters
Indicates that one entity is involved with, concerned about, or responsible for legal issues, processes, or obligations related to another entity or context.
-
E.
hasLegalRight
Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding 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_69ca836320e48190b5cf585b90a322c4 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fb8aab88190befed16301e08efc |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:44 p.m.