Triple
T24281469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebraska Court of Appeals |
E605550
|
entity |
| Predicate | hasRetentionMethod |
P30153
|
FINISHED |
| Object | retention elections |
—
|
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: retention elections | Statement: [Nebraska Court of Appeals, hasRetentionMethod, retention elections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRetentionMethod Context triple: [Nebraska Court of Appeals, hasRetentionMethod, retention elections]
-
A.
retentionMethod
chosen
Indicates the method or strategy used to retain or keep something (such as data, customers, or resources) over time.
-
B.
canRetain
Indicates that one entity has the ability or permission to keep, hold, or maintain possession or control of another entity over time.
-
C.
judgesRetentionMethod
Indicates that one entity evaluates or assesses the method another entity uses for retaining or keeping something.
-
D.
leafRetention
Indicates whether an entity retains its leaves (e.g., remains evergreen) or sheds them seasonally.
-
E.
hasRollover
Indicates that one entity’s state, value, or benefits are carried over or extended into a subsequent period or 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5227888190b1713af150fa30a1 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.