Triple
T33449123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alabama Claims arbitration |
E856586
|
entity |
| Predicate | implementedRule |
P6249
|
FINISHED |
| Object | due diligence standard for neutral states |
—
|
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: due diligence standard for neutral states | Statement: [Alabama Claims arbitration, implementedRule, due diligence standard for neutral states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedRule Context triple: [Alabama Claims arbitration, implementedRule, due diligence standard for neutral states]
-
A.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
-
B.
isRuleGoverned
Indicates that an entity’s behavior, structure, or operation is determined and constrained by explicit rules or formal regulations.
-
C.
usesRulesFrom
chosen
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
-
D.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
E.
assumedRuleOf
Indicates that one entity is presumed or taken to hold authoritative control, governance, or dominion over another entity, typically without definitive confirmation.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:37 a.m.