Triple
T32132470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jefferson Pierce |
E820686
|
entity |
| Predicate | fightsCrimeIn |
P112256
|
FINISHED |
| Object | Freeland |
—
|
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: Freeland | Statement: [Jefferson Pierce, fightsCrimeIn, Freeland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fightsCrimeIn Context triple: [Jefferson Pierce, fightsCrimeIn, Freeland]
-
A.
featuresCrimeSyndicate
Indicates that something includes, involves, or prominently depicts a crime syndicate as part of its content or structure.
-
B.
isVigilante
chosen
Indicates that an entity takes the law into their own hands, acting outside official authority to pursue or punish perceived wrongdoers.
-
C.
policeCharacter
Indicates that one entity serves as a police officer or law-enforcement figure in relation to another entity.
-
D.
pursuesCrimeType
Indicates that an entity (such as a law enforcement body or individual) actively investigates, targets, or prosecutes a specified type of crime.
-
E.
fightsUsing
Indicates that one entity engages in combat or conflict by employing another entity as its weapon, tool, or method of fighting.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9726c848190bd8a36c32c389f2e |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:29 a.m.