Triple
T1572425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brandenburg v. Ohio |
E33569
|
entity |
| Predicate | establishedTest |
P30704
|
FINISHED |
| Object | imminent lawless action test |
—
|
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: imminent lawless action test | Statement: [Brandenburg v. Ohio, establishedTest, imminent lawless action test]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedTest Context triple: [Brandenburg v. Ohio, establishedTest, imminent lawless action test]
-
A.
establishesTest
Indicates that an entity creates or sets up a test or testing procedure for another entity.
-
B.
appliedTest
Indicates that a test has been administered or carried out on a particular subject or object.
-
C.
commonTest
Indicates that two or more entities share the same test, testing procedure, or evaluation in common.
-
D.
testsIn
Indicates that one entity conducts or performs tests within, on, or using another entity.
-
E.
establishedAs
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
- F. None of above. chosen
Provenance (4 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_69a885f11b048190935025a035302715 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907ba63c88190b60c14dec8d1e40f |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a9607716b4819092187f8c08daaf31 |
completed | March 5, 2026, 10:52 a.m. |
Created at: March 4, 2026, 7:27 p.m.