Triple
T7111636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Servicemembers Civil Relief Act |
E165719
|
entity |
| Predicate | providesProtectionIn |
P74614
|
FINISHED |
| Object | civil judicial proceedings |
—
|
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: civil judicial proceedings | Statement: [Servicemembers Civil Relief Act, providesProtectionIn, civil judicial proceedings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesProtectionIn Context triple: [Servicemembers Civil Relief Act, providesProtectionIn, civil judicial proceedings]
-
A.
providesProtectionAgainst
Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
-
B.
protectionType
Indicates the kind or method of protection that is applied to or associated with an entity.
-
C.
protects
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
D.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
E.
hasProtectionPurpose
Indicates that something is intended or designed to serve a protective function or goal.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5edf89c8190a069b35ff7768165 |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e456e89481908df42a1b4232a4a0 |
completed | March 27, 2026, 8:11 p.m. |
Created at: March 27, 2026, 2:43 p.m.