Triple
T26572867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garcetti v. Ceballos |
E666870
|
entity |
| Predicate | clarifiesTest |
P41881
|
FINISHED |
| Object | Pickering balancing test |
—
|
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: Pickering balancing test | Statement: [Garcetti v. Ceballos, clarifiesTest, Pickering balancing test]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clarifiesTest Context triple: [Garcetti v. Ceballos, clarifiesTest, Pickering balancing test]
-
A.
clarifiesThat
Indicates that one entity explains or makes another entity more understandable by removing ambiguity or confusion about it.
-
B.
clarifiesStandard
chosen
Indicates that one entity explains, specifies, or makes more precise the meaning or application of a given standard for another entity.
-
C.
clarifiesTermsOf
Indicates that one entity explains, defines, or makes more precise the terms or conditions associated with another entity.
-
D.
establishesTest
Indicates that an entity creates or sets up a test or testing procedure for another entity.
-
E.
theoryTested
Indicates that a theory has been subjected to evaluation or experimentation to assess its validity or accuracy.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f614a519f0819087c98f8b48d14cce |
completed | May 2, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:59 a.m.