Triple
T26818636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Criminal Syndicalism Act |
E675184
|
entity |
| Predicate | scrutinizedIn |
P1394
|
FINISHED |
| Object | Whitney v. California |
—
|
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: Whitney v. California | Statement: [California Criminal Syndicalism Act, scrutinizedIn, Whitney v. California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scrutinizedIn Context triple: [California Criminal Syndicalism Act, scrutinizedIn, Whitney v. California]
-
A.
scrutinyMethods
Indicates the methods or procedures used to examine, inspect, or critically evaluate something.
-
B.
isInspected
Indicates that an entity is examined or checked by another entity to assess its condition, quality, or compliance.
-
C.
reviewedFor
Indicates that one entity has examined or evaluated another entity for a specific purpose, standard, or context.
-
D.
reviewedBy
chosen
Indicates that an item, work, or action has been examined and evaluated by a specific agent or reviewer.
-
E.
investigatedFor
Indicates that an entity is the subject of an investigation concerning a suspected involvement in another entity (typically a crime, incident, or wrongdoing).
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61a87b34081909f7e7276e9e9c82b |
completed | May 2, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 4:53 a.m.