Triple
T264231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Trust Services |
E5819
|
entity |
| Predicate | usesLegalAuthority |
P125
|
FINISHED |
| Object | federal Indian law |
—
|
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: federal Indian law | Statement: [Office of Trust Services, usesLegalAuthority, federal Indian law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLegalAuthority Context triple: [Office of Trust Services, usesLegalAuthority, federal Indian law]
-
A.
usesLegalCode
Indicates that one entity applies, references, or operates under a particular legal code in its actions or regulations.
-
B.
hasLegalEffect
Indicates that an action, document, or condition produces recognized legal consequences or enforceable rights and obligations.
-
C.
legalBasis
chosen
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
-
D.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
E.
legalAuthorityLevel
Indicates the degree or rank of formal legal power or jurisdiction an entity holds in relation to another or within a given context.
- 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_69a258dd8ea08190ac554a1cc8dfd8c3 |
completed | Feb. 28, 2026, 2:54 a.m. |
| NER | Named-entity recognition | batch_69a25d8e809881908a58c9a4e3ba07c3 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6e07748190834022a65ba6d803 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.