Triple
T25361356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor Peirce |
E635974
|
entity |
| Predicate | hasCriminalRecordIn |
P80418
|
FINISHED |
| Object | Victoria |
—
|
NE NERFINISHED |
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: Victoria | Statement: [Victor Peirce, hasCriminalRecordIn, Victoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCriminalRecordIn Context triple: [Victor Peirce, hasCriminalRecordIn, Victoria]
-
A.
hasHadCriminalConviction
Indicates that an entity has previously been found guilty of a criminal offense through a legal process.
-
B.
hasCriminalCharacter
Indicates that an entity possesses traits, behaviors, or a reputation associated with criminal activity or unlawful conduct.
-
C.
criminalRecord
chosen
Indicates that an entity has a documented history of criminal offenses or convictions recorded by an authority.
-
D.
associatedWithCrimeRecordOfUser
Indicates a relationship where something is linked to, or derived from, the crime record belonging to a specific user.
-
E.
hasCriminalElement
Indicates that the subject involves, contains, or is associated with an illegal or criminal component, activity, or characteristic.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 1:36 p.m.