Triple
T1572429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brandenburg v. Ohio |
E33569
|
entity |
| Predicate | standardReplaced |
P28535
|
FINISHED |
| Object | clear and present danger 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: clear and present danger test | Statement: [Brandenburg v. Ohio, standardReplaced, clear and present danger test]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardReplaced Context triple: [Brandenburg v. Ohio, standardReplaced, clear and present danger test]
-
A.
replacedStandard
chosen
Indicates that one standard has been superseded or taken the place of another standard.
-
B.
standardBefore
Indicates that one standard must be satisfied, applied, or occur earlier in sequence or priority than another standard.
-
C.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
D.
standardApplied
Indicates that a particular standard, rule, or guideline has been put into effect or used as the basis for an action or decision in the relationship.
-
E.
standardMaintained
Indicates that a specified standard is being upheld, preserved, or kept in compliance over time within the relevant context.
- 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_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. |
Created at: March 4, 2026, 7:27 p.m.