Triple
T655561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fulton v. City of Philadelphia |
E11639
|
entity |
| Predicate | appliedTest |
P17991
|
FINISHED |
| Object | strict scrutiny |
—
|
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: strict scrutiny | Statement: [Fulton v. City of Philadelphia, appliedTest, strict scrutiny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedTest Context triple: [Fulton v. City of Philadelphia, appliedTest, strict scrutiny]
-
A.
testsIn
Indicates that one entity conducts or performs tests within, on, or using another entity.
-
B.
tests
Indicates that one entity examines, evaluates, or checks another entity or condition to determine its properties, performance, or correctness.
-
C.
appliedBy
Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
-
D.
commonTest
Indicates that two or more entities share the same test, testing procedure, or evaluation in common.
-
E.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f4d57688190a9515ac494a97b22 |
completed | March 1, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69a49d121cec81909986c91291bb4ca8 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49ee356c0819085e2e82831cf1360 |
completed | March 1, 2026, 8:17 p.m. |
Created at: March 1, 2026, 7:36 p.m.