Triple
T25784442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gonzales v. Carhart |
E649381
|
entity |
| Predicate | typeOfChallenge |
P31731
|
FINISHED |
| Object | facial challenge to federal statute |
—
|
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: facial challenge to federal statute | Statement: [Gonzales v. Carhart, typeOfChallenge, facial challenge to federal statute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfChallenge Context triple: [Gonzales v. Carhart, typeOfChallenge, facial challenge to federal statute]
-
A.
challengeType
chosen
Indicates the specific category or kind of challenge associated with an action or relationship between entities.
-
B.
hasChallenge
Indicates that an entity faces, experiences, or is confronted with a particular difficulty, obstacle, or problem.
-
C.
challengeTo
Indicates that one entity issues a challenge or dare for another entity to face or respond to.
-
D.
challengeUndertaken
Indicates that an entity has accepted and is actively engaging in a specific challenge or demanding task.
-
E.
challenger
Indicates that one entity is challenging or opposing another, typically by initiating a contest, dispute, or competitive confrontation.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 22, 2026, 5:53 a.m.