Triple
T752791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gitlow v. New York |
E15485
|
entity |
| Predicate | hasRelatedTest |
P16406
|
FINISHED |
| Object | clear and present danger test (discussed in dissent) |
—
|
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 (discussed in dissent) | Statement: [Gitlow v. New York, hasRelatedTest, clear and present danger test (discussed in dissent)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedTest Context triple: [Gitlow v. New York, hasRelatedTest, clear and present danger test (discussed in dissent)]
-
A.
relatedTest
chosen
Indicates that there exists some form of connection or association between one test and another.
-
B.
testsIn
Indicates that one entity conducts or performs tests within, on, or using another entity.
-
C.
appliedTest
Indicates that a test has been administered or carried out on a particular subject or object.
-
D.
commonTest
Indicates that two or more entities share the same test, testing procedure, or evaluation in common.
-
E.
isRelatedName
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64d7d2c8190a6059adcb8fbd34f |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a501c4cc81908de6d63e3d4f60d7 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.