Triple
T18366731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standing Bear |
E440066
|
entity |
| Predicate | legalRightAffirmed |
P95247
|
FINISHED |
| Object | habeas corpus |
—
|
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: habeas corpus | Statement: [Standing Bear, legalRightAffirmed, habeas corpus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalRightAffirmed Context triple: [Standing Bear, legalRightAffirmed, habeas corpus]
-
A.
hasLegalRight
Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding another entity.
-
B.
legalDocumentRelatedToRights
Indicates a relationship where a legal document concerns, defines, or affects the rights or entitlements of entities involved.
-
C.
legalConclusion
chosen
Indicates that a situation, set of facts, or argument leads to or supports a specific determination or outcome under the law.
-
D.
legalAuthorityIn
Indicates that an entity holds official legal power, jurisdiction, or governing authority within a specified area or domain.
-
E.
protectsRight
Indicates that one entity safeguards, upholds, or defends the legal or moral rights of another entity.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5174e834481909453ba25561d1b1d |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:38 a.m.